On Thursday 10 October 2002 14:49, Jan Schaumann wrote: > Sean 'Shaleh' Perry <[EMAIL PROTECTED]> wrote: > > I like to have the wm act consistently. We do not let you move the > > window too far off screen nor does maximization cause the window to > > exceed the screen size. Why then should resizing be different? > > It strikes me as a differen thing: > I can not move a window further past the border of the screen, b/c my > mouse can't go there[1]. If we allowed continuous workspaces (so that > moving a the mouse to one border of the screen makes it switch to the > bordering workspace (of exists)) we certainly would want to be able to > keep moving the window. >
but we don't (and I don't we will) support such behavior. > Maximization is different b/c it has a single goal: make the window > fill the screen (+/- toolbar, slit whatever options you set). the > 'maximum' in this action is (to me) the maximum viewable window, not the > hard maximum that's possible. > true, I was using it as an example of window change. > > There is also the questionable benefit of window information being > > offscreen. > > Imagine a window without scrollbars showing information that exceeds the > screen size. (Hey, I'm not saying I use this feature all the time ;-) > I call this a misbehaving program. > > What (if anything) does NETWM say abut resizing? > it doesn't say anything it leaves policy to the window managers. > -Jan > > [1] Interesting side-note on this: If you move a window out of the > screen using bbkeys, then alt-tab away from it and then alt-tab back to > it, it appears in the center of the screen. the focus code does a check to ensure the window is within the screen's bounds and if not it moves it. The idea is that it makes little sense to focus something you can not see. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] List archives: http://asgardsrealm.net/lurker/splash/index.html Trouble? Contact [EMAIL PROTECTED]
