-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse support #43
Comments
It's not impossible, but it's pretty low on my list of priorities at the moment. Handling mice properly on Wayland comes with some annoyances, like having to load a cursor theme and such. Also if I do implement it, it'll probably be just for clicking on a result, as handling text selection etc. is likely better left to more advanced tools. Either way, I probably will get round to looking at it at some point, so I'll leave this open for now. Thanks for the suggestion! |
I'd also like to suggest being able to exit out of tofi whenever clicking out it's window, should mouse support be added, someday. This is because I use, among other things, tofi as a launcher for cliphist, launching it from a waybar icon as such: Anyway, seeing as I can already kind of start tofi with the mouse, it would be nice to be able to interact with it also with the mouse. P.S.: nevermind the difference between the number of entries announced by the waybar tooltip and the number displayed on tofi; I had to copy the screenshots to paste them here. |
In my opinion, this, along with, optionally, @7ff04da4aa6ac37197e249299066ac30's suggestion of exiting tofi when clicking out of the window (and/or perhaps right-clicking on it) would be all that is really needed out of this kind of program as far as mouse support goes, at least, for the vast majority of use cases for Tofi. The lack of mouse support for selecting and clicking on items is basically the only thing that kept me from fully switching from instantOS' dmenu fork "instantMENU" to Tofi for a long time, even if that means running instantMENU as an Xwayland program, which is far from ideal (and I also do not use most of the fancy functionalities of instantMENU anyway). I still am switching to Tofi now, as Xwayland menu programs are causing me more and more trouble, and because Tofi is awesome overall and really freaking fast, but I wholeheartedly agree that basic mouse support would be the most welcome, even if it is not a priority. Fun fact: Having mouse support in other similar programs allowed me to go into my custom program launcher, scroll down, click on the virtual keyboard entry, allowing me to use my laptop when my keyboard suddenly decided to unalive. It is really a supremely niche use case, but one that saved the day, and that is great for accessibility. |
No please 🙇♂️, no mouse support it's actually a neat feature. |
Not being able to use the most common non-touch pointing device in the entire world with this kind of menu program is not a feature; In fact, it can easily be argued to be a bug. There are reasons why even If mouse support gets implemented in any way someday, nothing stops you from not using it, nor does it stop you from forking and removing mouse support from it. |
I actually agree with you on the importance of pointing devices (I used one to click on your profile picture out of pure curiosity).
Yeah, you're right, mouse support is optional in dmenu. Actually, this conforms with their philosophy. And I quote:
My reasons for choosing tofi can be summed up in the repo description: Tiny dynamic menu for Wayland. So, because of that, I don't think mouse support should be a priority. But in the end, it's not about what foonathan nor barbara wants, it's about a good set of defaults that align with the project's philosophy. And I finally quote @philj56:
I don't want to start a holy war about something like this, but I like simple software. XoXo, |
Hi, I have implemented basic mouse support (#208). |
Hello. Is it possible to add mouse support?
The text was updated successfully, but these errors were encountered: