[Development] [Interest] Qt 5 worries - A plea for software rendering fallbacks
Simon Hausmann
simon.hausmann at nokia.com
Thu Oct 27 12:21:18 CEST 2011
On Thursday, October 27, 2011 11:48:52 AM ext Frans Klaver wrote:
> Hi,
>
> On Thu, Oct 27, 2011 at 11:37 AM, Schimkowitsch Robert
> <Robert.Schimkowitsch at andritz.com> wrote:
>
> > I see there's no Qt5-Feedback list up and running, so I'll post here in the
> > meantime.
>
> AFAIK all qt5 feedback can go onto the development mailing list now.
> It's probably best to continue the discussion there.
>
> Cheers,
> Frans
>
>
> > I have really big issues with the "OpenGL ES" decision. I have developed a
> > 2D-graphic engine for Windows (kinda similar to GraphicsView in its
> > abilities), based on OpenGL.
> >
> > Over the years, I had tons of trouble with
> > -) Memory or resource leaks in graphic card drivers
> > -) Crashes when using Remote Desktop
> > -) Drivers only working in single monitor mode
> > -) Issues where the graphic output would look different on a certain graphic
> > card (an absolute no-go for a technical application that people depend on)
> >
> > After battling those issues for several years, I had to drop back to the
> > Microsoft OpenGL 1.1 software driver. Fortunately, it is quite fast enough
> > for what I need. It does have it's flaws, but at least I know them and can
> > work around them.
> >
> > Please, take it from someone who has been trough the fires: Provide a pure
> > software rendering fallback, at least for QWidget and QGraphicsView-based
> > applications!
> >
> > Allow the developer to choose this fallback!
That fallback exists, doesn't it? I mean, QWidget and QGraphicsView contine
to use the raster paint engine by default for the backing store in Qt 5. Nothing
changed here :)
On a related note: The Chromium folks seem to be rather successful in shipping
WebGL on Windows on top of Angle ( http://code.google.com/p/angleproject/ ).
It would be nice to try out Angle for QtQuick/OpenGL in Qt 5 on Windows.
Simon
> > It makes all the difference between testing the resulting application once,
> > or on every graphic card with every driver version a customer might use.
> > Which is obviously impossible.
More information about the Development
mailing list