[XFCE 0000031]: After remote X login with different screensize correct panel location isn't detected.
[email protected] Tue, 23 Dec 2003 13:11:50 +0000 (GMT)
| Newsgroups | gmane.comp.xfce.devel |
|---|---|
| Message-ID | <[email protected]> |
The following bug has been RESOLVED. ======================================================================= http://bugs.xfce.org/view_bug_page.php?f_id=0000031 ======================================================================= Reporter: daniel ciaglia Handler: huysmans ======================================================================= Project: XFCE Bug ID: 0000031 Category: panel Reproducibility: always Severity: minor Priority: normal Status: resolved Resolution: fixed ======================================================================= Date Submitted: 2003-12-06 10:26 GMT Last Modified: 2003-12-23 13:11 GMT ======================================================================= Summary: After remote X login with different screensize correct panel location isn't detected. Description: OK, actually c&p from my eMail to the dev-list (Msg-ID:<[email protected]>): Logging in with remote X (X -query orwell) into my default desktop with an different display size (800x600 vs. 1280x1024), doing some work, shutting down the laptop and using the workstation as usual the next day gives me this position of the panel: http://www.ciaglia.de/tmp/desktop.jpg When working remote, the panel sets itself to the lower border of the screen, but not centered. Back to normal, it's a little bit lazy and stays at its position in the center of the screen. Well, I haven't looked at the code but wouldn't it be the cleaner solution to use the set preferences (center at the bottom) at every startup then waitinig for the final *click* in the settings menu? ======================================================================= ----------------------------------------------------------------------- huysmans - 2003-12-23 13:11 GMT ----------------------------------------------------------------------- fixed in 4.0.2