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. 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. 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. This applies to the main program and add-on modules to which the customer is licensed. I believe this is ultimately because of Qt wanting to be a non-console (windowed) program, and the debug normally working with console output. The HYDRUS Maintenance subscription will provide you with the following benefits: Access to the latest version of HYDRUS, including all updates and upgrades, which also means a free upgrade to a new major version of HYDRUS (e.g., from version 5.x to 6.x). Two debug modes fail to build, and another appeared to go ok, but then does not boot the exe correctly. It browses with tags instead of folders, a little like a booru on your desktop. The hydrus network client is an application written for Anon and other internet-fluent media nerds who have large image/swf/webm collections. Hmm, yeah, I did not have luck building different kinds of debug build for the client. This is a thread for releases, bug reports, and other discussion for the hydrus network software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |