25 Jan
2014
25 Jan
'14
8:30 a.m.
On 01/25/2014 02:03 AM, Timothy Pearson wrote:
The GTK2 engine and the GTK3 engine have radically
different designs. The
GTK3 engine uses the new TQt3 style API, whereas the old GTK2 engine
creates TQt3 widgets in the background and copies their contents to the
screen. The GTK3 engine is therefore much more efficient and uses much
less memory, but as GTK3 is not yet feature complete, glitches remain in
the rendering.
Thanks Tim,
While I've got you, if you get a chance, take a look at the k3b bug:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1858
It is an invalid use of incomplete type mpc_decoder... and error:
'mpc_streaminfo_init' was not declared in this scope issue. I don't think it
will be bad for a smart guy to fix :-). The 2 biggies I'm waiting on are k3b,
then I think k9copy will build. Thanks.
--
David C. Rankin, J.D.,P.E.
> With 2 apps is there some logic that tells
gtk-2 and 3 apps to use the
> different engines to create different configs on icon-set or widget-style
> changes? Are there now two configs in thelpcenter?
Same config. You can
enable or disable each engine independently from the
same TDE control center module.
Tim