Hi Carsten,
On Tue, 2004-08-03 at 07:20, Carsten Neumann (D. Stricker) wrote:
> Hi,
>
> Matthias Stiller wrote:
> > On Tuesday 03 August 2004 10:29, Carsten Neumann (D. Stricker) wrote:
> > after looking at that code of mine, I agree, can't imagine another
> >
> >>reason to write a whole class if not to work around a Qt-bug ;). Anyway,
> >>in recent version that workaround now seems to break :((
> >>Now the interesting question is what code to use ? Do we have a
> >>recommended version ?
> >
> > Another possible solution would be to work around it with a qtversion
> > ifdef. I
> > am pretty confident that qt already has something like this. It is not the
> > best solution, but things like this happen from time to time.
>
> agreed, but how do I figure out the qt version that first fixed the bug?
> The line of 3.x.x releases is pretty long already and the changelog of
> almost every version mentions fixes in qtable, but sadly nothing that
> matches the problem at hand exactly :(
> So, the real reason why I had hoped for a more radical decision here is,
> that I'd like to avoid compiling qt-versions and testing the widget
> against them for days... ;)
If it's really just an ifdef I would put it in using the knowledge we
have right now and leave it at that. In the future I'd expect people to
use only the most current version of QT, so if it works for the current
and the later ones it should be ok. Testing against all existing old
versions sounds pretty tedious and not very efficient to me.
Dirk
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
