Quote:
Originally Posted by DiapDealer
I'll be interested to see what they're doing. Even if their software puts its own Qt libraries in the system path, it shouldn't affect Sigil. The only thing I can think of that would cause problems is if their installation software sets some Qt-specific environment variables system-wide. That would be bad.
We used to have problems with incompatible versions of OpenSSL being on the system path, but we stopped compiling OpenSSL support into Sigil's Qt on Windows to avoid that.
What would probably help the most is profiling a Sigil launch with Dependency Walker.
Thanks for the heads-up though.
P.S. I wonder if the evaluation copy of Diskeeper Home would exhibit the problem? There are no "gotchas" with installing/uninstalling the software is there? I don't want to have to setup a new virtual Windows machine just to do a little testing.
|
Thanks for the reply:
There are no "gotchas" I'm aware of with Diskeeper. Conduciv is a good company with excellent tech support, so when they recontact me I'll ask about your best test options to make sure. They should be more than willing to help.
I'll also ask if Diskeeper sets some Qt-specific environment variables system-wide. I'll let you know either here, or by private message if you prefer.
I've never used Dependency Walker before, but I just downloaded it. Is there a tutorial? I didn't see one on their website. Am I right to assume you'll want scans of the Sigil
and Diskeeper exe files, once Diskeeper is reinstalled?
Thanks,