Re: Window History Placement

On Fri, 2003-01-10 at 10:41, Benjamin Kahn wrote:
> Hi Matthias,
> On Fri, 2003-01-10 at 09:03, Matthias Clasen wrote:
> > Another clever thing with the number part of the id is this "reshuffling",
> > which seems to implement something like the n best positions for a window with
> > name/class/role, although the spec is not clear enough here. What happens if
> > I start two instances of an app (so that the wm remembers two positions
> > n/c/r/1 and n/c/r/2. If I now close 1 and move 2, will the wm still remember two
> > n/c/r positions, or is
> > the old n/c/r/2 position forgotten when 2 is moved ?
> 	Window histories are never forgotten(*) unless they are replaced by a
> new matching window in that spot.  (Which doesn't really count as being
> forgotten since, in that case, a window will have been placed with the
> old window's characteristics and will only be saved if the user modifies
> the window in some way.)  
> 	Thus, in the case above, there will be two window states being stored
> -- the new placement of 2 (now 1) and the old placement of 2.  (Which
> will be used if a second window is opened.)  In tests where users were
> told to pay attention to window placement and given a little background
> on what was happening, this seemed to surprise them at first, but feel
> comfortable quickly.  But it might be better to forget the old window
> history when a window is promoted in the numbering scheme.

* -sigh-  The structure I'm using and the file format I'm using store a
last updated field which allows me to expire old entries if I choose
to.  My implementation does not expire window histories at all, but this
list could obviously grow quite large over time.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]