Re: Partial width struts

[Rob Adams <robadams ucla edu>]

That would work, though the backward compatibility would not be as
complete, since many WMs probably have code similar to that in metacity
which checks for exactly four values or it will ignore the property.

(well now that I look at it it will actually just check for four values
then segfault, but that's beside the point).

Newer apps could suddenly stop working on older WMs, though newer WMs
would work with any apps if we don't change the name.  But maybe that's
OK.  Probably not though.

-Rob

On Sat, 2003-06-07 at 16:44, Ben Jansens wrote:
> On Sat, Jun 07, 2003 at 02:49:48PM -0700, Rob Adams wrote:
> 
> [...]
> 
> > _NET_WM_STRUT, left, right, top, bottom, CARDINAL[4]/32
> > 
> > This property is deprecated, and may be removed from future versions
> > of this Specification.  It has been replaced with
> > _NET_WM_STRUT_PARTIAL. Clients MAY set this property using just the
> > first four values of the _NET_WM_STRUT_PARTIAL property to ensure
> > backward compatibility with Window Managers supporting older versions
> > of the Specification.
> > 
> > _NET_WM_STRUT_PARTIAL:
> > 
> > _NET_WM_STRUT_PARTIAL, left, right, top, bottom,
> > left_start_y, left_end_y, right_start_y, right_end_y
> > top_start_x, top_end_x, bottom_start_x, bottom_end_x
> 
> Hey, 
> 
> Just wondering what the rationale is behind making a new property
> (_NET_WM_STRUT_PARTIAL), rather than just specifying that _NET_WM_STRUT
> how has 12 values, but if only 4 are present, that the WM should treat it
> appropriately. For example, this is how the starting_corner extention to
> the _NET_DESKTOP_LAYOUT property was handled.
> 
> Ben