Closed GoogleCodeExporter closed 8 years ago
It sounds like a Qt plugin issue. How are you running DViz - through Qt
Creator? What
version of Qt are you using?
Original comment by josiahbryan@gmail.com
on 7 Dec 2009 at 5:44
DViz was a release build, and was run standalone outside of Qt. I'm using Qt
4.5.3,
with Qt Creator 1.2.1; no change since the last working build. As far as I am
aware,
my build environment is 100% the same as it was before. I also just checked my
PC's
changelog and I've only installed or upgraded three things since then, and I
doubt
any would be related (they are FeedDemon, Recuva, and SpeedFan).
I tried running from within Qt, and it works fine! And tried running again
outside
of Qt; the folder whose icons were populated while running from within Qt still
looked fine (so the cache works), but other folders still did not load their
icons.
Any idea which plugin(s) I might be missing?
Original comment by kpr...@gmail.com
on 8 Dec 2009 at 12:01
The release build that you're running outside of Qt Creator - its probably in
dviz/src/release, right? Is there a "plugins" sub-folder within the 'release'
folder?
If there is, what sub-folders are inside 'plugins'?
If there is no 'plugins' folder within the 'release' folder where dviz.exe is,
you
can just copy the entire Qt plugins folder from its install path - probably
C:\Qt\2009.05\Qt\plugins or something like that. I'm not at a windows PC where
I can
check right now - on linux, the install is: /opt/qtsdk-2009.05/qt/plugins/.
Just copy the entire 'plugins' folder from Qt's install location into the
'release'
folder where the dviz.exe is that you're running. Try testing again and see if
it
works with JPGs now.
Original comment by josiahbryan@gmail.com
on 8 Dec 2009 at 1:01
Adding the plugins/imageformats folder (and its contents) to the
dviz.../src/release
folder fixed the problem. Thanks for the suggestion. I would consider this
issue
closed.
Original comment by kpr...@gmail.com
on 9 Dec 2009 at 12:07
Closing issue.
Original comment by josiahbryan@gmail.com
on 13 Dec 2009 at 3:34
Original issue reported on code.google.com by
kpr...@gmail.com
on 6 Dec 2009 at 12:21