22 Feb
2012
22 Feb
'12
1:50 a.m.
Yep, that sounds like the problem. No problem, i would imagine you would
prefer to leave qt3 to the side and develop tqt3 instead and i am happy to
wait.
Tomorrow i will rebuild under tqt3 and see how she goes.
Thanks.
On Wed, Feb 22, 2012 at 12:43 AM, Timothy Pearson <
kb9vqf(a)pearsoncomputing.net> wrote:
*Moodin is a
separate thing altogether so it has to be installed
separately
in order to use some of the splashes.*
Yes, it is in the applications folder and builds no problem. I have since
found (after rebuilding everything again) that the themes are broken for
me. All themes.
If i run: kcmshell ksplashthememgr
I get the error message that the plugin:Default is not installed. The
error
in the konsole says that the library could not be loaded. All libraries
are
in place. The same error appears for any theme, stating that the plugin
for
the theme could not be loaded. It was working fine a few weeks ago.
Not sure why, or how yet.
Jay
Are you building under qt3 instead of tqt3? If so I think I know what the
problem is, but don't yet have a way to fix it.
Many TDE .desktop files contain a type string, e.g. TQString, that allows
the plugin loader to know how to interpret library paths, etc. via the
TQVariant class. These were recently renamed to fix loading under tqt3,
but I am fairly certain this broke loading under qt3.
The easiest fix is to modify qt3, but I am very hesitant to do that...
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting