Screen fading + dual screen setup

[ndlarsen]

Hi.

Oblogout 0.2, as well as current "0.3" from git, doesn't seem of fade out properly on a dual screen setup. Only the screen on which oblogout is displayed is faded. Notice the "double" tint2 bar on the faded screen (dunno if the is a tint2 issue) and that it is displayed clearly as if oblogout is rendered in a lower layer. While running lxpanel instead of tint2, lxpanel is displayed clearly as if oblogout is rendered in a lower layer only, no double bars.
Screenshots attached.

[ndlarsen@master ~]$ oblogout -v
2009-12-01 15:27:42,953 - root - INFO - Using config file /etc/oblogout.conf
2009-12-01 15:27:42,961 - OpenboxLogout - DEBUG - Shortcut Options: [('suspend', 'U'), ('lock', 'K'), ('hibernate', 'H'), ('logout', 'L'), ('shutdown', 'S'), ('cancel', 'Escape'), ('restart', 'R')]
2009-12-01 15:27:42,961 - OpenboxLogout - DEBUG - Setting cmd_hibernate as pmi action hibernate
2009-12-01 15:27:42,962 - OpenboxLogout - DEBUG - Setting cmd_lock as gnome-screensaver-command -l
2009-12-01 15:27:42,962 - OpenboxLogout - DEBUG - Setting cmd_safesuspend as safesuspend
2009-12-01 15:27:42,962 - OpenboxLogout - DEBUG - Setting cmd_suspend as pmi action suspend
2009-12-01 15:27:42,962 - OpenboxLogout - DEBUG - Setting cmd_logout as openbox --exit
2009-12-01 15:27:42,962 - OpenboxLogout - DEBUG - Setting cmd_shutdown as sudo shutdown -h now
2009-12-01 15:27:42,962 - OpenboxLogout - DEBUG - Setting cmd_restart as sudo reboot
2009-12-01 15:27:42,963 - OpenboxLogout - DEBUG - Validating button: cancel
2009-12-01 15:27:42,963 - OpenboxLogout - DEBUG - Validating button: logout
2009-12-01 15:27:42,963 - OpenboxLogout - DEBUG - Cmd Value for logout: openbox --exit
2009-12-01 15:27:42,963 - OpenboxLogout - DEBUG - Validating button: restart
2009-12-01 15:27:42,963 - OpenboxLogout - DEBUG - Validating button: shutdown
2009-12-01 15:27:42,963 - OpenboxLogout - DEBUG - Validating button: suspend
2009-12-01 15:27:42,965 - OpenboxLogout - DEBUG - Validating button: lock
2009-12-01 15:27:42,966 - OpenboxLogout - DEBUG - Cmd Value for lock: gnome-screensaver-command -l
2009-12-01 15:27:42,966 - OpenboxLogout - DEBUG - Validated Button List: ['cancel', 'logout', 'restart', 'shutdown', 'suspend', 'lock']
2009-12-01 15:27:42,966 - OpenboxLogout - DEBUG - No compositing, enabling rendered effects
2009-12-01 15:27:42,977 - OpenboxLogout - DEBUG - Stepping though render path
2009-12-01 15:27:43,053 - OpenboxLogout - DEBUG - Rendering Fade

[ndlarsen (usenet)]

Forgot to mention that it's rev. 101 in trunk

[Andrew Williams (nikdoof)]

Yes, it seems we need to enforce foremost window order to jump above the panels, strangly i've never had this issue while using tint2 or lxpanel myself.

As for the dual screen part, at the moment it gets the screen dimensions, this must include only the current screen and not all screens bound to that desktop.

self.window.resize(gtk.gdk.screen_width(), gtk.gdk.screen_height())

[ndlarsen (usenet)]

I appreciate your reply.
So for dual screen setup, it's a gtk related limitation, then? Is this understood correct? Btw, rereading the originl post, I might have come off a bit "harsh". Not my intention. Thumbs up for a otherwise nice piece of SW.

[Andrew Williams (nikdoof)]

No, its a oblogout issue. At the moment it only takes into account a singular screen, oblogout should be checking if gtk.Screens > 0 then working out the total area for the background.

The issue with this is that with the layout of the window the buttons will stretch across both screens, so i'll have to take into account being able to "fix" the buttons to the primary screen.