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
{{ message }}
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.
Im not sure what can be done with IOS apps and their keyboards...
It would be great if I didnt have to drill down 2 levels to get to the '+' and '@' keys.
I can think of two ways to possibly make an easier experience to enter new context projects. Either would be enough, both together might be even better:
a more narrow spacebar and add these two keys to the right of it
after pressing project or context buttons, allow text to be entered, filtering as the user types, add new if no match is found
Or is there a simple way to avoid having to press '?123' then '#+=' each time I want a new context / project? Even the selector widget without autofilter is going to be tough to use once I have a few tens of these, I'm concerned...
Thanks for considering this issue, and let me know if there is already a good way to do this that im missing.
(I also have your android app, its only 1 click deep and I mostly only read on that device, so I'm quite happy with that UX)
The text was updated successfully, but these errors were encountered:
Im not sure what can be done with IOS apps and their keyboards...
It would be great if I didnt have to drill down 2 levels to get to the '+' and '@' keys.
I can think of two ways to possibly make an easier experience to enter new context projects. Either would be enough, both together might be even better:
Or is there a simple way to avoid having to press '?123' then '#+=' each time I want a new context / project? Even the selector widget without autofilter is going to be tough to use once I have a few tens of these, I'm concerned...
Thanks for considering this issue, and let me know if there is already a good way to do this that im missing.
(I also have your android app, its only 1 click deep and I mostly only read on that device, so I'm quite happy with that UX)
The text was updated successfully, but these errors were encountered: