After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 625233 - GDK_NATIVE_WINDOWS + Windows: resize problem + button problem
GDK_NATIVE_WINDOWS + Windows: resize problem + button problem
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
2.20.x
Other Windows
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-07-25 13:28 UTC by michael.goffioul
Modified: 2018-02-10 04:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description michael.goffioul 2010-07-25 13:28:43 UTC
When defining GDK_NATIVE_WINDOWS=1, resizing produces incorrect redraws in various widgets (text editor [1], drawing area, gtlgkarea...). Moreover, buttons do not do anything when clicked with the mouse (focusing with Tab + Space still works).

I tracked the resize problem down to _gdk_window_move_resize_child (gdkgeometry-win32.c), where is_move and is_resize are always 0. So the native window is not resized correctly. This happens because width/height fields from GdkWindowObject have already been updated in gdk_window_move_resize_internal (gdkwindow.c) prior to calling the move_resize member of the underlying impl window.

I didn't investigate the button/mouse problem, sorry.

[1] See post on http://mail.gnome.org/archives/gtk-list/2010-July/msg00094.html
Comment 1 michael.goffioul 2010-07-30 21:37:54 UTC
Further debugging about the button problem shows that the click signal is not fired, because button->in_button is 0 in gtk_real_button_released(). This indicates that enter-notify-event does not reach the button when using native windows.

Button does not turn to depressed mode for the same reason.

Hope this helps.
Comment 2 Matthias Clasen 2018-02-10 04:37:35 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.