Re: move/resize from keyboard

On 18 Oct 2001, Havoc Pennington wrote:

> Mathias Hasselmann <mathias hasselmann gmx de> writes: 
> > 	Havoc, I you continue to make pagers thumber and thumber we might
> > reach the point were it makes sense to built in the pagers into the window
> > manager again...
> I think it makes sense to have pagers separate, there are just a few
> missing pieces right now to get the UI right. Window managers need not
> support all the hints if they don't want to, but I think we should
> have the hints in the spec, rather than doing GNOME/KDE extensions.

	Well. Ok. So let's discuss the meaning of those flags:

>  +#define _NET_WM_MOVERESIZE_SIZE_KEYBOARD     9   /* size via keyboard
>  +#define _NET_WM_MOVERESIZE_MOVE_KEYBOARD    10   /* move via keyboard

	Yes, I understand that sizing by keyboard/taskbars has to be
handled separatly since you have no information about the resizing
anchor. It has to be determinated by keyboard/mouse actions. But shouldn't
this flag be called


? Simply 'cause the resize mode you want is typical but not limited to
keyboard triggerd resizing.

	I don't understand how _NET_WM_MOVERESIZE_MOVE and

<offtopic newThread="if interested">

	Well. Since you want to catch up nearly all extended window manger
hints I maybe also should specify IceWM's tray hints in a clean
manner... At the moment it's handled by a simple but somehow quarzed
"_ICEWM_TRAY_OPTION" hint. Guess in NetWM language it should be specified
by additional _NET_WM_STATE hints:


 - IceWM's current ignoreTray would be mapped to the empty set
 - MinimizeToTray would be { _NET_WM_STATE_MINIMIZE_TO_TRAY }
 - Exclusive would be the set { _NET_WM_STATE_MINIMIZE_TO_TRAY,
 - _NET_WM_STATE_ALWAYS_IN_TRAY doesn't exist in IceWM yet.


PGP/GnuPG:     1024-Bit DSA: ID 55E572F3, 1024-Bit RSA: ID EAAF7CF1

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