On Thursday 02 December 2004 19:17, Kuba Ober wrote:
> > This only works when you statically bind in the QT library and you don't
> > change the interface at all. Or are willing to rebuild the QT libs for
> > yourself.
> Why? If your code implements a QTable class with all the other things it
> needs, then the linker simply won't even put the QTable-related symbols in
> the import table in the executable if you're using a dynamicly-bound Qt. So
> it doesn't really matter if you're using static or dynamic Qt. Obviously,
> the linker has to believe that your symbols take precedence over those
> available in the import library for the DLL that you're using, but at least
> with gnu binutils it's simply a matter of ordering things right.
I neither needed to rebuild Qt, not did I need to completely take QListView
into my own sources. Just the QToolTip subclass did the trick, and creating
it with QListView->viewPort() as its parent. This way, the default internal
tooltip object gets replaced by my modified one, thus fixing the problem.
Nothing complicated, no messing with binutils or static Qt builds at all,
just standard Qt programming.
My opinions may have changed, but not the fact that I am right.
-- Ashleigh Brilliant