@Japhir
Hi,
Tab key on a keyboard is used to advance the cursor to the next tab stop.
Wiki: http://en.wikipedia.org/wiki/Tab_key#Modern_usage
On computer keyboards, the enter key in most cases causes a command line, window form, or dialog box to operate its default function. This is typically to finish an "entry" and begin the desired process, and is usually an alternative to pressing an OK button.
Wiki: http://en.wikipedia.org/wiki/Enter_key
We set Enter to autocomplete the currently typing, Tab to jump to next attribution.
Best regards,
Doit.im Team
When adding a new task I often make the "mistake" of hitting tab to autocomplete the currently typed context, project or tag (or priority etc.). This causes me to have to click in the window again and add the suggestion manually or with the return key. It is really counterintuitive for me to hit return halfway through adding a task, since it normally completes the task-entering-process.
So I would really like it if the auto-complete selection key would be changed from return (enter) to tab. This is more compatible with the way users usually interact with auto-completion.
Kind regards,
-
01/26/2015 09:29#1PRO
-
01/26/2015 11:28#2PRO
Yes, I know how it handles it when adding a task via the menu. There it operates as it should IMO. But when quick-adding a task, e.g. typing "do the dishes @h.." and it suggests @home which i'd like to select quickly and continue to type in the !high or a tag or something, I think it would make more sense to auto-complete with tab. (Such as in the command line for Unix machines etc.)
I think this is more logical and congruent with what you say, since you can't move to another field in this view anyway (there are none, only the quick-add field! So pressing tab actually does nothing but stop you from typing!).
I hope you understand what I mean :). -
01/27/2015 03:32#3PRO
@Japhir
Hi,
Thank you for your feedback. We will do a research on this issue.
Best regards,
Doit.im Team