Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"invalid drawable" errors #396

Closed
johnhaddon opened this issue Jun 24, 2013 · 2 comments
Closed

"invalid drawable" errors #396

johnhaddon opened this issue Jun 24, 2013 · 2 comments
Labels
bug Issues representing bugs

Comments

@johnhaddon
Copy link
Member

These apparently harmless errors appear in the terminal when running on OS X. It appears to be related to the GLWidget, and a problem whereby Qt tries to initialise a GL context before the native mac widget exists. Some investigation seems to suggest that hiding the widget on creation and then finding an appropriate time to show it might work. Or perhaps embedding the QGLWidget inside a container in the GafferUI.GLWidget, and only showing it once the parent has been shown.
johnhaddon added a commit to johnhaddon/gaffer that referenced this issue Jan 22, 2014
@johnhaddon
Fixed "invalid drawable" error messages on OS X.
144e93a 
I had hoped that this fix would make the previous commit unnecessary, but testing shows that they address different problems and both are needed.

Fixes GafferHQ#396.
johnhaddon added a commit to johnhaddon/gaffer that referenced this issue Jan 22, 2014
@johnhaddon
Fixed "invalid drawable" error messages on OS X.
aaf4c2d 
I had hoped that this fix would make the previous commit unnecessary, but testing shows that they address different problems and both are needed.

Fixes GafferHQ#396.
@andrewkaufman andrewkaufman mentioned this issue Jan 27, 2014
Merged
johnhaddon added a commit to johnhaddon/gaffer that referenced this issue Jan 28, 2014
@johnhaddon
Fixed some "invalid drawable" error messages on OS X.
c2eafc0 
I had hoped that this fix would make the previous commit unnecessary, but testing shows that they address different problems and both are needed. Additionally, although this fixes the initial "invalid drawable" messages on startup, they still appear later on when switching between fullscreen and not-fullscreen. This goes some way to addressing GafferHQ#396, but I suspect it'll be very hard to fix it completely without patching Qt in some way.
@johnhaddon
Copy link
Member Author

@themissingcow, do you get these "invalid drawable" messages at all? I think they date to an older version of Qt, in which case we should close this ticket.

@themissingcow
Copy link
Contributor

@themissingcow, do you get these "invalid drawable" messages at all? I think they date to an older version of Qt, in which case we should close this ticket.

Never seen them...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issues representing bugs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@themissingcow @johnhaddon @andrewkaufman