![]() ![]() Since you are comfortable with running from python source, did you happen to already have python or C++ Qt already on your system? I have had a couple reports before about system-wide Qt environment variables sometimes upsetting hydrus's private Qt. If this works for you, that narrows down the problem. ![]() This obviously makes it easy to figure out which sidecar goes with which file. They typically share the same basic filename-if the master is Image123456.jpg, the sidecar will be something like Image123456.txt or. Does it boot? Does it give you a different error? Different versions of pyinstaller work better or worse for certain unusual situations, such as running the program with a symlink. Sidecars are files that provide additional metadata about a master file. However, here is a different build, using an older version of Please try extracting and running that on your desktop or similar. There is supposed to now be a 'windowed' dialog hook to display the debug traceback, but I am only getting problems through it. I believe this is ultimately because of Qt wanting to be a non-console (windowed) program, and the debug normally working with console output. Two debug modes fail to build, and another appeared to go ok, but then does not boot the exe correctly. I wrote a Python 2.7 script that acts as an adapter between Hydrus and FlipFlip. Hmm, yeah, I did not have luck building different kinds of debug build for the client. Thanks for introducing me to Hydrus Network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |