[Qt-interest] Clarification on "out of scope" closed bug

[Frank Hemer]

On Wednesday 19 January 2011 07:55:58 Andre Somers wrote:
> Op 19-1-2011 5:29, Thiago Macieira schreef:
> > On Tuesday, 18 de January de 2011 16:54:19 Allen Bierbaum wrote:
> >> Our entire application is based upon using QGraphicsProxyWidgets.  We
> >> use them to place widget panels (floating windows, etc)  in a scene
> >> overlaid on  an OpenGL canvas.  This lets us do compositing and many
> >> other advanced visual effects and back when we created it, the
> >> recommended way to do this was QGraphicsProxyWidgets.  If this isn't
> >> recommended/supported any more, I hope there is a relatively easy
> >> migration path so we don't end up down a dead end.
> >
> > The migration path is to redo your widgets entirely in Graphics View.
>
> Auch!
> How is that for being able to count on Qt as a stable platform?
> QGraphicsProxyWidget has been introduced in 4.4, released in the first
> half of 2008. That is less than 3 years ago. And now, you tell your
> users that what they have come to rely on is suddenly not supported
> anymore? There is no "depricated" label to be found for that class.
>
> What are the promises made by Sebastian Nyström at the 2010 DevDays that
> investments in the desktop area would not go down worth, if this is what
> happens in practice? [1] Can we rely on QML being supported three years
> from now, or will we again need redo our components in the next great,
> yet immature, Qt technology again to expect to work against supported code?
>
> I really love working with Qt, but I really don't like the way users
> with existing investments in Qt seem to be left in the cold because
> their little corner is not the next hot thing any more.

Let me undergird this argument - to me it appeared like a big step into the 
right direction being able to add the rich set of standard widgets provided 
by qt to a graphicsview.
And now it seems like this is about to be obsolete in the (near?) future?!

I myselfe have been tackled by this as some bugs related to the use of 
Qt::AA_NativeWindows flag are also currently closed as 'out of scope'.

It might be that the use of this flag is rather rare - but anyway in case a 
braille display or alike are installed on a system, this flag gets 
automatically set and thus widgets in combination with graphicsview behave 
rather 'strange'.

I sure read the note in graphicsproxywidget warning about the use in a 
high-performance scenario ... but this does not at all sound like 
a 'do-not-use'.

So please: keep up the good work ... and don't start to leave your customers 
start to freeze ...

Frank