unity's restore from maximize is breaking the positioning of overlay thumb

Bug #732091 reported by Andrea Cimitan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
overlay-scrollbar
Fix Released
Medium
Unassigned

Bug Description

after restoring from a maximized window, thumb is misplaced, you need to do a configure event like a resize in order to place it correctly.
does not happen without unity, does not happen with metacity

Related branches

Andrea Cimitan (cimi)
Changed in ayatana-scrollbar:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Andrea Cimitan (cimi) wrote :

Figured out what's going on... it's a smspillaz's question.
So, you know unity is removing the titlebar on maximize, but after restoring the titlebar is added "after" the configure-event, so event->x and event->y of the configure event connected to the scrollbar lack of the pixels of the titlebar (and the scrollbars are higher of the amount of pixels of the titlebar)

Changed in ayatana-scrollbar:
status: Confirmed → Triaged
Revision history for this message
Andrea Cimitan (cimi) wrote :

After a long discussion with jason, it seems his bug is a way harder than it seems, and maybe long to fix.
We need to connect to the parent window of the toplevel window, which is a xwindow, create a gdk_x11_foreign window and hook up for its configure_event.
This is the hardest part, because adding a filter_func for each scrollbar (so, twice the filter func for each scrollbar), is a terrible idea. we should try to figure out a way to connect to a global filter func that tells each scrollbar to update the window coordinates when the xconfigureevent of the parent window of its toplevel window is received. (please kill me :-\)

Revision history for this message
Andrea Cimitan (cimi) wrote :

*this bug

Andrea Cimitan (cimi)
Changed in ayatana-scrollbar:
status: Triaged → Fix Committed
Andrea Cimitan (cimi)
Changed in ayatana-scrollbar:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.