Closed GoogleCodeExporter closed 9 years ago
Original comment by ready...@gmail.com
on 13 Oct 2012 at 11:34
This is intended behaviour - originally, the /change command would be
auto-filled if a user single-clicked a task - to prevent accidentally
overwriting a user's input. Could be changed if desired (or more complex logic
added to check if the command is an auto-inserted one, and not an "organic"
command.)
Original comment by jchen...@gmail.com
on 13 Oct 2012 at 11:37
Use a flag to determine if the current command was auto-generated (a simple
bool variable would do). If it is auto-generated, it can be replaced by new
auto-generated command, if the user accidentally double clicks on the wrong
entry. If user changes the command in the textbox, the flag should be
automatically set to false, and should be treated as a user command.
Original comment by ready...@gmail.com
on 13 Oct 2012 at 11:40
Removed check in revision ea4f18a25f22 on ui branch. Double-clicking a task
will now auto-fill a /change command for that task in the Command Bar,
regardless of whether there is pre-existing text there or not.
Rationale: though the possibility still exists that a user accidentally
double-clicks a task and wipes out text they have input in the Command Bar,
this is instantly undoable through the standard Ctrl-Z shortcut (restoring the
text previously in the Command Bar.)
Original comment by jchen...@gmail.com
on 16 Oct 2012 at 1:18
Original issue reported on code.google.com by
ready...@gmail.com
on 13 Oct 2012 at 11:33