[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 188728] maximized panel size in different resolutions
From:       <vprints () gmail ! com>
Date:       2009-07-10 12:05:26
Message-ID: 20090710120526.BBDAC14A0A () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=188728


vprints@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vprints@gmail.com




--- Comment #17 from  <vprints gmail com>  2009-07-10 14:05:11 ---
(In reply to comment #8)
> [PlasmaViews][2][Sizes][Horizontal1920]
> max=-1,-1
> min=-1,-1
> offset=0
> size=640,320
> 
> so it says that the size last seen for screen width of 1920 is 640x320, which
> is rather short and tall :)
> 
> the way plasma-desktop manages panel size restoration is this:
> 
> * if there is a size previously set for this resolution, then use that
> * if there isn't, then check if on the previous resolution the panel was
> maximized; if so, then maximize it on this new resolution
> * if there is no size for this resolution and the panel wasn't maximized, then
> just keep the panel the size it is
> 
> then:
> 
> * make sure the panel isn't any wider/taller than the current screen

Hi Aaron,

we are currenlty trying to deploy KDE4 in our university, and we have a little
problem with this behavior- all our users are authenticated and user profiles
hold centrally, and we have mutiple computer lab sets with multiple
configurations of monitors and other hardware, and to us it seems it would be
better to set the width of the panel in percentage of the screen with.
As we also understand this is not the behavior everybody would want, but could
it be made configurable for example with a similar line in the appropriate
plasma config file:

"save_panel_with_percentages=1"

so in big deployments sysadmins coud simlpy turn the percentage option on
without the need of changeing the default behavior for upstrem KDE.

Of course, if we could somehow store different plasma configurations for
different machines inside the same user account and have plasma automagically
load the correct one when user is logging in to that computer would be the best
of the best for our use case. Phonon might also benefit from this one since
currently it distracts a user logging in to a different computer than previous
login with a frightening message that the sound card has dissapeared =) but it
actualy isn't, its just where it was before, only the user and his profile
information is now moved on to another computer with different sound card :D

I will make a new / comment existing proper bug report about that behavior of
phonon.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]