Bug 1731125 Comment 19 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Screencast: I managed to get a transparent EGL window on Nvidia.
At the moment I just hardcode `framebutter_config_attrib_list[] = { EGL_CONFIG_ID, 0x008,` etc., but the conclusion seems to be:
If eglGetConfigAttrib EGL_NATIVE_VISUAL_ID (0x82) is what gdk_x11_visual_get_xvisual(gdk_screen_get_rgba_visual) gave us (0x82), then it's the correct Nvidia egl framebuffer config (0x8).

First I tried to set the visual in realize(), but then eglCreateWindowSurface failed with EGL_BAD_MATCH.
gtk_widget_set_visual() must be called with the window_widget_ptr from gtk_window_new(),
not with the widget_ptr inside the g_signal_connect realize function.

I'll attach the testcase after cleaning it up a bit.
Revision 1 by
on 
Screencast: I managed to get a transparent EGL window on Nvidia.
At the moment I just hardcode `framebuffer_config_attrib_list[] = { EGL_CONFIG_ID, 0x008,` etc., but the conclusion seems to be:
If eglGetConfigAttrib EGL_NATIVE_VISUAL_ID (0x82) is what gdk_x11_visual_get_xvisual(gdk_screen_get_rgba_visual) gave us (0x82), then it's the correct Nvidia egl framebuffer config (0x8).

First I tried to set the visual in realize(), but then eglCreateWindowSurface failed with EGL_BAD_MATCH.
gtk_widget_set_visual() must be called with the window_widget_ptr from gtk_window_new(),
not with the widget_ptr inside the g_signal_connect realize function.

I'll attach the testcase after cleaning it up a bit.

Back to Bug 1731125 Comment 19