Comment 34 for bug 36189

The fact is that this is not something an average user should worry about.
Most people don't care about the placement of these objects and applets.

The fact that these settings can be changed by anything other than direct
user intervention (ie: screen resolution) should be fixed.

After many times of unlocking, repositioning, and locking objects and
applets I became fed-up. I wrote a Python script to set the panel layout the
way I like it.

We need to consider the appeal of Ubuntu to ordinary users depends on
consistent behaviour. There is a mandate to my the interface as user
friendly as Mac OS X.

With regards to this bug, even Windows is a better experience.

I think a GUI to address this only further complicates matters.

I advocate tracking down apps that modify any gconf entries in the
'/apps/panel/' schema. A good first step would be to look at the 'Display
Preferences' code or any code that adjusts screen resolution and be sure
that it is considerate of this issue (not modifying 'right stick' or
'position' values of any objects or applets).

Does this sound reasonable?

Can someone point me to the source code responsible for changing screen
resolution?

On Fri, Apr 24, 2009 at 3:48 AM, David Fokkema <email address hidden> wrote:

> @Sandro:
> I agree with Aidan. It's not only when adding applets. However, I just now
> only managed to break things when switching to lower resolution, log off,
> log in, switching to higher resolution. Without the log off, log in, I tried
> to restart the panel between, before and after switching resolutions, but
> nothing broke. It did, however, after log off, log in. I don't know why.
> Maybe the problem is not even in the gnome-panel code directly.
>
> It would be really, really nice to get a list of which code touches the
> gconf settings, and when.
>
> @Aidan: Thanks! I agree with both your points.
>
> --
> Applets do not scale well with changing resolution
> https://bugs.launchpad.net/bugs/36189
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
John Haitas
<email address hidden>