[9fans] rio bottom wctl cmd ...

[9fans] rio bottom wctl cmd ...

[Philippe Anel]

Hello,

    While adding a 'bottom' entry to the rio menu3 (in order to move
the clicked window to the *bottom*), I realized something already
well documented :

rio(4):
                The top and bottom commands do not change
                whether the window is current or not; the others
                always make the affected window current.

    So if the *current* window is moved to the *bottom*, it means that
window will still be the recipient of keyboard and mouse input ... even
behind other windows (i mean partially or totally hidden).

    In that case, we can't *top* another window, say one of those
in front of the *current* *bottom* window, with a button click (Wakeup).

    I find that feature ... disconcerting.

    I suggest to patch rio in order to raise the right window when clicking,
even if the *bottom*'ed window is still the recipient of inputs. I think
reordeing
the window array (see dat:319) would be sufficient.

    Any idea ?

    Phil;

Re: [9fans] rio bottom wctl cmd ...

[Sape Mullender]

> rio(4):
>                 The top and bottom commands do not change
>                 whether the window is current or not; the others
>                 always make the affected window current.
>
>     So if the *current* window is moved to the *bottom*, it means that
> window will still be the recipient of keyboard and mouse input ... even
> behind other windows (i mean partially or totally hidden).

Current refers to keyboard input, not mouse input.

	Sape

Re: [9fans] rio bottom wctl cmd ...

[Philippe Anel]

Sape Mullender wrote:

>>rio(4):
>>                The top and bottom commands do not change
>>                whether the window is current or not; the others
>>                always make the affected window current.
>>
>>    So if the *current* window is moved to the *bottom*, it means that
>>window will still be the recipient of keyboard and mouse input ... even
>>behind other windows (i mean partially or totally hidden).
>>
>>
>
>Current refers to keyboard input, not mouse input.
>
>	Sape
>
>
>
>
>
This is not true. I mean, in the current rio, current refers to both
keyboard input and mouse input.

rio(4):

Wctl: ... current (make the window the recipient of keyboard and mouse
input)

    Phil;