On Thu, Jun 06, 2002 at 09:08:11AM -0400, Derek Cunningham wrote: > On Wed, Jun05,02 23:45, Sean 'Shaleh' Perry wrote: > > > > On 06-Jun-2002 Derek Cunningham wrote: > > > Hmm... so I notice that when you maximize, then resize, the maximize button > > > will re-maximize (ie: maximization was turned off after the resize). > > > However, if I maximize the window, then MOVE it, maximization is not turned > > > off. For consistency sake, wouldn't that be a good idea... it also seems > > > logical. > > > > > > > it makes sense (to me) that you might move a maximized window. Also why does > > the fact that you moved it affect the fact that it is maximized? It still is > > full size. > > > > hmm... I guess I associate 'maximized' with two things: > > 1) the 'maximized' program will take up as much screen realestate as > possible (of course, with the new .65 series, this is defined by the struct). > > 2) the maximized window is in a centered position on the screen. > > I see no reason why I would want to move a maxmimized window, as moving it > puts some of the windows off screen. I propose that maximized windows should > not be moveable (config option?).
There is no way that would fly for a large number of users. An option could be added to make it so, but the entire behavior could not be changed without ruining a lot of people's day. > > > > ----- > > > > > > ok... another thought. Would it be desired to have resizing snap to the > > > screen (well, the struct) edges? > > > > > > > this could be done with some work. > > that would be very cool, and again, adds to the consitency of blackbox. xOr -- I am damn unsatisfied to be killed in this way.
msg07307/pgp00000.pgp
Description: PGP signature
