GNOME Bugzilla – Bug 139779
Panel entries with fixed position jump around
Last modified: 2010-12-28 13:40:36 UTC
Distribution: Debian testing/unstable Package: gnome-panel Severity: normal Version: 2.4.x Synopsis: Panel entries with fixed position jump around Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.4.x Description: Description of Problem: I have all items in the panel set to fixed position ("Sperren" in German). Now, I removed a symbol somewhere on the right side. Strangely ALL icons left of this place moved up to the right now. Only the Menues (Applications ("Anwendungen") and Actions ("Aktionen")) stayed in their places on the left of the panel. Steps to reproduce the problem: 1. Set ALL the items in the panel to "fix position" ("Sperren"). 2. Remove one somewhere on the right. Actual Results: Automagically all items on the left (including the "Command Line" applet) jump to the right, filling the gap -- in spite of being set to fixed positions. Expected Results: All other items should with fixed positions should stay where they are. Not fixed items may move ok. How often does this happen? Every time I tried Additional Information: After this unexpected behaviour it is very uncomfortable to reset things to original positions manually, because for each item I have to do this: 1. Unset the fixed position for all items. 2. Move all items to their old positions. 3. Reset the position to fixed for all items. I suggest an option for the panel to set/unset the "fix position" for all items in one go. Even better would be an option to select more than one item for moving/changing. For this, a rubberband or the CTRL key might come in handy. -- [de] Das Museum fuer falsche Fehlermeldungen: http://www.moffem.de/ [en] The Museum Of Faulty Error Messages: http://www.moffem.de/ [de] Suchen im Internet: http://www.abc-onlinesuche.de/ [de|en] Anti-Spam - Spam-me-not: http://www.zapyon.de/spam-me-not/ ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-12 03:49 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Could you attach before and after screenshots to explain what you mean? Thanks
Reopening: I think the problem here is that objects with right_stick=yes and that are locked move if an item at their right is removed. I'll try to reproduce.
I feel that gnome-panel behaves strangely in terms of applet position all the time... A set of rules like the way firefox's toolbars can be edited is much simpler to figure out. I think that the panel should behave more like firefox in this respect... with applets and launchers remembering the order they are in from left to right (or top-bottom), rather than however the position is worked out at the moment. The problem with doing this is how are gaps in the panel addressed? in firefox there are 2 types of gap, a fixed width gap, and a filler gap (more than one filler gap can be added, and they will be equal in length)... Should I file a new bug for this?
I can't reproduce this specific bug anymore, anyway comment #3 has some interesting suggestions that may be useful. I think that filing a new bug for those and closing this (if the issue is actually solved) would be the best option.
I am confirming this bug on GNOME 2.20.1 Ubuntu 7.10 Gutsy Gibon i386
This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it. Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field? Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE after 6 weeks.
Actually, I did not encounter this bug for a couple of years now. Thought the matter was long closed. :-) Cheers, Andreas