-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add Fly-Pie-like Hover Mode #303
Comments
Hi there! Thanks for the idea! However, I am afraid that I do not fully understand your suggestion. In Fly-Pie, there was a thing which I called "Hover Mode" but this is not yet implemented for Kando. For now, we have three different possibilities to select items in Kando:
Now what is your suggestion? You can use any of these modes at any time. You can select an item by clicking on it, you can select the next by dragging it, you can select the third by holding a modifier key and moving your mouse. You can decide on your own, which to use and you can seamlessly transition between them. I think there is no need to disable any of these possibilities forcefully as you cannot use them accidentally...? |
i meant being able to select different modes for different pie-menus... with the possibility of having this option at sub-menus too! |
I still don't get it. Why do you want to disable one of the interaction modes? They are all available at the same time. |
yeah but what if i have the "hover mode" activated and i don't want it at X and Z menu? |
Ahh, so you're really talking about the Hover Mode from Fly-Pie? That's not yet available in Kando. And it is not necessarily planned right now as I am not sure if it's actually used by many people. Do you think that it should be added to Kando? |
oh well, i assumed that we were typing about Fly-Pie as there's a warning on Kando about being at a prototype phase... anyway, i'm suspect to reason if hover-mode should be added... believe or not i got custom pie-menus fired by different keyboard layers on a per app basis :3 ¶ the hover-mode although, feels a natural progression or feature one would want after setting and memorizing the menu directions?! sure we can hold the key that opens it and release after positioning the mouse but i still think tapping keys is more ergonomic than holding ¶ if hover-mode is implemented, it makes a lot of sense to define which menu should have this mode, as well threshold/distance for activation... and not a general toggle that works on every menu |
Yeah, in Fly-Pie the hover mode is only experimental. In Kando, we can implement it properly, but it has a pretty low priority for me. |
@luqtas Typically Github issues should consist of one subject, however, this issue mentions both hover mode + threshold settings. I'd say that the threshold settings are an independent subject. Additionally because the issue primarily focuses on Hover-mode and is titled "Add Fly-Pie-like Hover Mode", I think that warrants a separate issue so I created one right here #568. Note: Based on the issue I made, Hover-Mode could be added as a separate menu behavior setting. This way, the threshold behavior settings would be applied regardless of whether you're using Marking-Mode, Turbo-Mode, or Hover-Mode. If you agree, then please add any threshold ideas there to keep things cleaner. I think the only thing missing there that you mentioned was the interesting idea of a dynamic/training setting (I didn't want to take credit for it so I didn't add it, but you're welcome to do so) :
|
would be cool if we have modes to (un)check on an individual basis, e.g. i mastered my media pie-menu, so i don't have to think much about selecting it... although the key to access that menu is the same i use to do backup/power operations (they are in different sub-menus) and those aren't mastered to the point that i could use it with the "hover mode"
as a bonus, maybe the more user uses a menu, the app can suggest at some point a lower threshold or even activating the "hover mode"? ¶ modifying anything should reset the variable...
The text was updated successfully, but these errors were encountered: