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
I am an avid user on tut on small screen+virtual keyboard (pinephone + pmos), and i totally love it!! <3
Though what may differ on a small device from a proper-size keyboard is that without hands resting on keyboard at all time, each keypress is a bit more "costly" and in some contexts more difficult to achieve.
I found out that very often, in order to scroll the content of a toot (also maybe a feature of small screen, as on bigger displays it is more rare that a toot displays on more than one screen), i was repeating the same sequence of keys... it's actually probably the action i do the more often besides navigating through lists:
entering view mode
scrolling down inside the toot
exiting view mode.
the "space" key, always accessible, isn't mapped yet. Would it make sense that it'd be mapped on this exact sequence of actions? It would have very minor impact if hit inadvertently, as it restores the UI in its previous state afterwards / it is potentially easy to implement as it is about serializing a bunch of existing functions (v, pg_dn, esc).
thus my suggestion:
space -> v, pg_dn, esc.
what do you think?
The text was updated successfully, but these errors were encountered:
I am an avid user on tut on small screen+virtual keyboard (pinephone + pmos), and i totally love it!! <3
Though what may differ on a small device from a proper-size keyboard is that without hands resting on keyboard at all time, each keypress is a bit more "costly" and in some contexts more difficult to achieve.
I found out that very often, in order to scroll the content of a toot (also maybe a feature of small screen, as on bigger displays it is more rare that a toot displays on more than one screen), i was repeating the same sequence of keys... it's actually probably the action i do the more often besides navigating through lists:
the "space" key, always accessible, isn't mapped yet. Would it make sense that it'd be mapped on this exact sequence of actions? It would have very minor impact if hit inadvertently, as it restores the UI in its previous state afterwards / it is potentially easy to implement as it is about serializing a bunch of existing functions (v, pg_dn, esc).
thus my suggestion:
space -> v, pg_dn, esc.
what do you think?
The text was updated successfully, but these errors were encountered: