- Moderator
- #91
@Anthony Vaughan If necessary, I can make Jira, branch for PullRequest, and after merge, make test build ...
Obviously, I don't know you handle to different sources that come to you.If necessary, I can make Jira, branch for PullRequest, and after merge, make test build ...
I have just had a quick look at the BAT file, and I think that it won't work for people who are running a 32-bit version of Windows -- the "Program Files" folder has the wrong name. I think that it should be:I have placed a zip file in the first post of this thread which can be used to install the refactor over the existing 1.29 release so that you can have a play with it.
Thank you for pointing that out. Sadly, for 64 bit machines this is not so simple because %ProgramFiles% points to C:\Program Files\.I have just had a quick look at the BAT file, and I think that it won't work for people who are running a 32-bit version of Windows -- the "Program Files" folder has the wrong name. I think that it should be:
- "C:\Program Files" on 32-bit Windows
- "C:\Program File (x86)" on 64-bit Windows
Certainly, if you can explain to me what to do. I really need to work with an example so I can test that everything is working properly but I don't do anything like that and don't know how to proceed.A single movie can consist of multiple DVDs, Blu-Rays, or files. Therefore, a mechanism for processing such information is made. There is only one movie in the database, but the file table contains all its files from 1 to H. And MP1 counts the duration and other data for these files. At the beginning of viewing there is a choice from which part to watch, etc.
Many people use this, and it cannot be broken. You can experiment yourself by making 2 files for the movie.
AJS has sent me code to do what you want so I've changed the batch file.Looking at the environment variables in Windows 10, it appears that the variable %ProgramFiles% probably has the required value. It is:
- "C:\Program Files (x86)" on 64-bit Windows 10
- "C:\Program Files" on 32-bit Windows (probably -- I cannot check at the moment).
Sorry. I should have been more clear.To integrate the changes into the main branch, we need the source code on GitHub. Then we can push the changes into the release. The file list will not help much, because someone has to make all the changes, but except for the author, it is unlikely that anyone can do this without errors.