View Single Post
Old 09-03-2009, 01:47 PM   #4
Valloric
Created Sigil, FlightCrew
Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.Valloric ought to be getting tired of karma fortunes by now.
 
Valloric's Avatar
 
Posts: 1,978
Karma: 350515
Join Date: Feb 2008
Device: Sony Reader PRS 505
Quote:
Originally Posted by mrmikel View Post
If the path is the problem is there a solution? VLC is not in the path but Roxio is and I think it uses Qt as well.
Hm... this is more complicated than it seems. The "main" Qt DLL's should be loaded from the Sigil directory no matter what is on your PATH, since Windows looks for DLL's in the app folder first. So that is not the issue.

What could be the issue is the loading of Qt plugins. Qt DLL's load some plugin DLL's dynamically. These are the ones located in the "codecs", "iconengines" and "imageformats" folders.

Now Sigil explicitly instructs that plugins should be loaded from those folders, but this could be overridden by plugins on the PATH. I'm not sure of the order in which Qt inspects the locations where the plugins could be loaded from. After a bit of research, it seems that if the application specifes a plugin search path with QCoreApplication::addLibraryPath() calls (as Sigil does), these are always searched first.

So it seems something else is your problem.

Last edited by Valloric; 09-03-2009 at 01:53 PM.
Valloric is offline   Reply With Quote