You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
When only using mouse or touch to watch videos, the controls overlay isn't very user-friendly or sometimes isn't functional (due to Windows issue, see below). This means that a keyboard may be effectively required to use the actions.
Issue
With a mouse, you need to hover over the smaller target of the current speed and then navigate to the right to click the action you want. If you accidentally move too vertical or horizontal, it collapses and you have to try again. This can be harder when using a touchpad where fine control of the mouse isn't as easy or if you're just not as accurate for whatever other reason.
With a touch device, Windows seems to do weird things with moving your mouse to that location or not. I don't really get it and it's super inconsistent at the OS level. The result is that sometimes tapping the current speed overlay results in it expanding and staying expanded (since it thinks your mouse it there). Other times, it ignores the tap or just flickers the expanded controller (likely because it thinks your mouse is elsewhere). Again, this is a Windows issue so it can't be resolved directly but it stems from the reliance on mouse location as the sole trigger for expanding.
Resolution
I'm just going to throw some ideas out there so someone else may have a better approach in mind:
This would be easier if the controls could be resized but it would also be nice to keep it expanded if desired. Perhaps clicking the current speed would trigger expand/collapse so it can be done on the fly while the current auto-expand/collapse remains. And maybe provide an option to configure the delay before collapsing.
Extra notes
This is may not be relevant if the control overlay were reworked for #1102 but I think the things I mentioned would be quicker tweaks. Combined with #1115 (specifically my comment expanding the scope), this would fully replace the need for a keyboard.
The text was updated successfully, but these errors were encountered:
Context
When only using mouse or touch to watch videos, the controls overlay isn't very user-friendly or sometimes isn't functional (due to Windows issue, see below). This means that a keyboard may be effectively required to use the actions.
Issue
With a mouse, you need to hover over the smaller target of the current speed and then navigate to the right to click the action you want. If you accidentally move too vertical or horizontal, it collapses and you have to try again. This can be harder when using a touchpad where fine control of the mouse isn't as easy or if you're just not as accurate for whatever other reason.
With a touch device, Windows seems to do weird things with moving your mouse to that location or not. I don't really get it and it's super inconsistent at the OS level. The result is that sometimes tapping the current speed overlay results in it expanding and staying expanded (since it thinks your mouse it there). Other times, it ignores the tap or just flickers the expanded controller (likely because it thinks your mouse is elsewhere). Again, this is a Windows issue so it can't be resolved directly but it stems from the reliance on mouse location as the sole trigger for expanding.
Resolution
I'm just going to throw some ideas out there so someone else may have a better approach in mind:
This would be easier if the controls could be resized but it would also be nice to keep it expanded if desired. Perhaps clicking the current speed would trigger expand/collapse so it can be done on the fly while the current auto-expand/collapse remains. And maybe provide an option to configure the delay before collapsing.
Extra notes
This is may not be relevant if the control overlay were reworked for #1102 but I think the things I mentioned would be quicker tweaks. Combined with #1115 (specifically my comment expanding the scope), this would fully replace the need for a keyboard.
The text was updated successfully, but these errors were encountered: