GNOME Bugzilla – Bug 349937
Graphical glitch when displaying the sidebar
Last modified: 2018-04-06 16:11:04 UTC
Please describe the problem: When the sidebar is displayed, its TreeView control can appear on top of the movie area for a fraction of a second before it is repositioned to the correct place. Steps to reproduce: 1. Open and a movie 2. Make the window the same size as the movie (resize 1:1) 3. Show and hide the sidebar 4. Make the window twice as big as the movie (resize 2:1) 5. Show the sidebar Actual results: The playlist TreeView appears on top of the movie (in its previous size and position) for a fraction of a second, then it gets moved to the sidebar, where it should be Expected results: Does this happen every time? Yes Other information: I am using the xine backend, with XVideo output.
I can't reproduce this. Does this also happen with the new property sidebar (in Totem 1.5.x)?
I checked out CVS HEAD and it still happens for me--though only when the sidebar is displaying the playlist, not the movie properties.
Created attachment 70234 [details] [review] totem-debug-349937.patch
The patch in comment 3 allows to show which portion of the display is getting damaged when the treeview is shown (with the xine-lib backend). As this doesn't happen with the properties window, I believe this is due to the treeview or the viewport used. I can produce a patch to the GStreamer backend to show the problem as well. gtk2-2.8.20-1
Created attachment 70235 [details] Damaged region circled
Also happens in 2.10.x Any chance to look at this? It looks quite unpolished...
It looks like it's the tree view's "bin window" which is shown at the old location before the size-allocate is handled that will move that window to the new and updated position. AFAIK GtkTreeView is handling these sub windows on exactly the same way as the other widgets using sub windows in GTK+, so I can't really point out where exactly the problem is at this point ...
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.