-
Notifications
You must be signed in to change notification settings - Fork 70
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.
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
framebuf: unix port: SDL window appears "inactive" #24
Comments
Thanks for the report, but I'm not sure what's being reported here. For me, it (SDL window?) doesn't appear to be "grayed out". You would need to explain better and/or provide steps to reproduce, screenshots, etc. |
Code to reproduce:
Here's a screenshot: |
Please use framebuf/ex_framebuf.py for testing. Here's how it looks for me: Nothing is ever grayed out. Window's close button doesn't work, that's expected. You need to go to console where you started the app, and press ctrl+c there. I encourage you to try to implement the calls mentioned in the SO post yourself, if not, I'll look into that when I have time. |
I'm using MATE on Ubuntu 18.04. But I believe initial version of the module was developed yet on 16.04, with MATE too of course. |
LOL, it's not even committed. Thanks for looking into this - when someone else but yourself gives it a try, a lot of goofs are uncovered ;-). It's now there, as framebuf/example.py |
OS: Ubuntu 16.04 LTS
When I create a FrameBuffer, a corresponding SDL window is created. However, it appears to be inactive or "grayed out" which is a bit annoying because colors appear different.
The text was updated successfully, but these errors were encountered: