Re: Draft 1.9b - some comments

[John Harper <john dcs warwick ac uk>]

Matthias Ettrich writes:
|     a) window managers know this property anyway. They have to because they
|         must dynamically change maximized windows whenever struts changes.
|         Obviously: Imagine a user running a maximized xterm and then 
|         starts a desktop panel. The window manager should adapt the size
|         of the maximized xterm to give the panel the required reserved space.

Well, they don't _have_ to do this -- personally I would find it really
annoying if the wm started resizing my windows just because some other
application has reserved part of the screen

(though I know other people feel strongly the opposite)

|
|> 
|> Also, the size of the maximum rectangle may vary depending on the
|> window being maximized, though this would be rare, 
|
|Please elaborate. I don't understand this.

If I have a window, and I've hinted to the wm that I'd like it to
remain unobscured by maximized windows, and I then maximize this window
itself, then obviously the original area of the window shouldn't be
included when calculating the maximized geometry

As I said above though, this would probably be very uncommon, and is
probably unimportant for your intended uses of the property..

	John