[Panel-devel] [Bug 153708] GL Applet errors with misleading text

[Zack Rusin]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=153708         




------- Additional Comments From zack kde org  2007-12-09 15:57 -------
The code all those examples (assuming bluemarble just uses glapplet and doesn't do anything stupid) is exactly the same so if one of them just works the others should as well. 
Having said that, the number and size of supported pbuffers is implementation dependent. We're using pbuffers inside glapplet because the only Qt paintdevices which are capable of creating hardware accelerated GL contexts are qglwidget and qglpixelbuffer. In future Plasma/Qt should have the ability to create a GL context per-executable. This way every applet wouldn't have to create it's own qglpixelbuffer (which are very heavy-weight objects) and be able to use qglframebufferobject.
I'm assuming fglrx has either 
- a nasty bug in pbuffers related code, 
- a really low limitation on the number of created pbuffers,
- fglrx ships with its own libglx and users are mixing it with the stock distro libglx causing those weird mishaps.
The bottom line is that the fact that this is with proprietary drivers makes it an uninteresting problem to be honest. The below attached patch should at least make it more consistant in its behavior, feel free to do whatever you want with it