G.
btw metadata are going to depend on the type of field. i'm handling specifically links, radiobuttons, checkboxes and buttons for the moment. the rest will have to be fine-tuned over...
also, copying when The Input is empty is not done. i'm planning at a later stage to copy the UI Element at the mouse position. like how you click at...
good point. this is handled by macOS itself. but not ideal yeah. will check what i can do, thanks for reporting.
> Not sure whether to ask this in here or kV. i've been wondering the exact same thing šļø > iām curious whether you have any plans to tackle scrolling...
can't be sure about Wooshy yet, but probably when you set up a new Mac and kV is not installed you're gonna feel it hard šļø
FWIW, there's now a new dedicated app for the scrolling from the creator of Vimac/Homerow: https://twitter.com/dexterleng/status/1563493043293995011 maybe that helps? still in the plans here. still not sure where it belongs...
yep. whatever makes people's lives better!
@haveanicedavid care to have a look? https://github.com/godbout/Wooshy.docs/discussions/69 gathering the brains. not about the scroll (yet), but somehow related to the "ecosystem". thanks!
> Have you considered making Normal mode kV (smooth) scroll on `hjkl` whenever the focus is not on text input for the accessibility strategy? Before discovering Wooshy I used [Vimari](https://github.com/televator-apps/vimari),...
hmm but now thinking about it again ( š ļø ) i think the main issue is that a `scroll area` is not really "reachable". like you can't click it. if...