[idea] [feature] a warp --hint3 that detects program elements similar to goondnight_mouse

[gitdexgit]

warpd --hint3 where you are trying to grab the elements of the browser, like how the plugin trydactile does it inside the browser. and potentially other applications.

This is really hard to achieve as programs are building with many stuff like GTK and qt...etc and it might require linux assistant features enables. the Toolkit assistance

There already exists something called goodnight_mouse(https://github.com/rpbritton/goodnight-mouse).

The problem

It has 3 main issues:

1. The issue with this one was that.... It needed some transparent compositor so the overlay doesn't show, but I found a way to remove it in the source code so that overlay isn't black and it looks like keyd...(the overlay issue was [QoL] remove the overlay and just use buttons instead. or make transparency not rely on compositor rpbritton/goodnight-mouse#7 )

2. The keys are sent to the application unlike warpd --hint so if the user has plugins or nvim motions they can be triggered.

3. The nature of apps in linux. Which means you probably need the Linux accessibility toolkit (for more info look for it in the wiki)

---

I suspect that maybe wayland should remove some of the limitations goodnight_mouse had... Similar to warpd... or maybe introduce more issues... so this is potentially another issue where it might never work on wayland but who knows.

I also saw the following fork of warpd (https://github.com/atuan26/warpd) by atuan26. managed to achieve similar feature. But I'm not sure if it's MacOS only.

reality

I think there is no need for such thing for the browser there is already an extension called trydactile that does that and more.

This feature is only good for other applications. But It just adds a lot of complexity So it's probably, the best option is to never use it and keeping it simple with warpd --hint in addition, warpd --hint2 is meant for prececie location within the box of hints...

So the best option so far I think is to optimize the warpd that we already have maybe increase the box count make the box in the shapes of the actual keys instead of a box behind the thing... maybe fill in the screen with just boxes why not... The user first has to look at a location on the screen so he doesn't need to know what's behind the screen for a split second.. .al the user need is more boxes probably... and better performance... more control... And compatibility with other applications that draw overlays. And getting the code more optimized so it takes less cpu for other apps to work well with warpd.