Re: zcurses mouse delay (not Re: Slurping a file)

[Ray Andrews <rayandrews@eastlink.ca>]

[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]


On 2024-01-13 21:03, Bart Schaefer wrote:
> Please don't reply/re-use an unrelated subject for a new question.
Pardon, thought I'd just sneak it in there.  Lazy.
> Patch going separately to zsh-workers.  Sorry, Ray, but you're out of
> luck without a rebuild.  I'll Cc you on the patch, it should apply to
> any zsh/curses module since zsh 4.3.5 of 2008-02-01.
>
It's time I started using the latest builds.  Usta do it, then I lost 
all  my notes during switch to new computer so now I'm with whatever 
Debian is offering (5.8).  BTW speaking of things that don't work -- 
from the manual:

- Any events that occurred as separate items; usually there will be just 
one.
An event consists of PRESSED, RELEASED, CLICKED, DOUBLE_CLICKED or 
TRIPLE_CLICKED

... AFAICT 'RELEASED' isn't there, a fast click reports 'CLICKED' a slow 
press (no release) reports 'PRESSED' and on release the 'mouse' array is 
null.  I worked around it, but since the 'fast click' time is said to be 
6ms by default, and I'm often a slow clicker, zcurses takes that as two 
separate mouse events -- which is why 'zcurses mouse delay' was of 
interest.  It's not hard to cope with but 'RELEASED' would seem more 
kosher than a null array.  Oh, and if it was ever of use -- say some 
notion of dragging something with the mouse -- the array's holding of 
the cursor position could be another reason the array should not be null 
on release.  We don't think of zsh as doing that kind of thing, but 
clicking and dragging something in a zcurses window could be an 
interesting party trick.  Watch out Thunar!




[-- Attachment #2: Type: text/html, Size: 2409 bytes --]