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 727650 - gtk drawing area fails to update (missing draw event)
gtk drawing area fails to update (missing draw event)
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-04-05 10:13 UTC by Mike Cornelison
Modified: 2017-10-09 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mike Cornelison 2014-04-05 10:13:18 UTC
Application is Fotoxx 14.04. A GTK notebook is used with tabs containing drawing areas inside scrolled windows. The program works on Ubuntu 13.10 and earlier (GTK 3.8) and fails on Ubuntu 14.04 beta (as of April 5) (GTK 3.10).

When the notebook tab is changed from F to G, the G tab's drawing area is not updated (thumbnail gallery page). Some prior content is present and the rest is background color only. Clicking elsewhere on the desktop and then clicking the window title bar (i.e. unfocus and refocus the window) causes the G tab to update correctly. Removing the default "double buffered" attribute from the G tab drawing area widget after it is created makes everything work correctly on Ubuntu 14.04 (GTK 3.10). However this fix fails on earlier Ubuntu releases (GTK 3.8 and earlier) - the G tab background is filled with content from the previous F tab.

This seems to be a problem with missing "draw" events or events with incorrect update regions. I have verified that draw events are NOT sent when the tab is switched into view but ARE sent when the window acquires focus. GTK may be saving and restoring content of tabs hidden and revealed, so I don't know if draw events are even needed when a hidden tab is selected. 

This could be same as bug #725089.

This bug is also filed in Ubuntu as #1302546.
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1302546
Comment 1 Daniel Boles 2017-10-09 14:01:14 UTC
(In reply to Mike Cornelison from comment #0)
> This could be same as bug #725089.

Was it, or does your one still occur?
Comment 2 Daniel Boles 2017-10-09 14:09:51 UTC
just saw your comment there: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1302546/comments/4 so closing as fixed.