Virtual keyboard immediately pops up on "Edit"

[Alexander Dietrich]

On the HTC Hero (and other touch-only phones, I presume) the on-screen keyboard immediately pops up when I select to "Edit" a task.

This is annoying in the case that I want to change the task priority or access fields below "Summary", because the keyboard is now blocking the view. So the first user action on the "Edit" screen is often to close the keyboard.

User experience could be much improved, IMHO, if there was at least an option to not give focus to the "Summary" field when opening the "Edit" screen, so that the virtual keyboard initially stays hidden.

I'm using an HTC Hero and Astrid 2.8.8.1.

[Bill Wohler (wohler)]

Ditto for me. I discard the keyboard 100% of the time when viewing a task and most of the time when editing a task since I'm usually editing the priority, due date, or note of an existing task--not the description. I view (not edit) tasks the majority of the time. The keyboard should only appear automatically if there is a single field. It's easy enough to bring up the keyboard with a trackball press (T-Mobile myTouch). Thanks!

[David Prieto (frandavid100-gmail)]

I was about to report this, too. This also bugs me when opening date / time settings, like when you press on "alerts → periodical reminders".

Since those settings have + / - buttons in addition to the number, I think the keyboard should not be brought up unless you actually press the number.

[Andrew Hunter (rexbron)]

David, please file another bug for that and nominate it for the 2.9.0 milestone.

[Alexander Dietrich (adietrich)]

I tested the fix in the new release. The keyboard doesn't open automatically on edit, but now I have to tap twice on the task name to bring it up. This is definitely the lesser evil (for me), but still a bit odd and not standard behaviour. I'm wondering if there may be a better way to fix this?

Anyway, thanks for releasing a new version so fast!

[Tim Su (tim-todoroo)]

Yeah, that should be a pretty simple fix. I realized this about an hour
after pushing out 2.9.0 =/

Alexander Dietrich wrote:
> I tested the fix in the new release. The keyboard doesn't open
> automatically on edit, but now I have to tap twice on the task name to
> bring it up. This is definitely the lesser evil (for me), but still a
> bit odd and not standard behaviour. I'm wondering if there may be a
> better way to fix this?
>
> Anyway, thanks for releasing a new version so fast!
>
>

--
*Tim Su
*Creator / Lead Engineer, Astrid & Todoroo
Todoroo, Inc | <email address hidden>*

*

[Bill Wohler (wohler)]

Hi Tim, thanks for the fix. I noticed the same thing that Alexander did, and was thankful for his workaround of using two taps to bring up keyboard.

Can you please make a couple of additional fixes that are related?

1. On the T-Mobile myTouch, pressing the trackball should have the same effect as tapping the field. When I press the trackball once, twice, or more, the keyboard does not pop up as it does in other applications.

2. Please consider popping up the keyboard immediately when creating a *new* task. I think in that case, the original behavior is desired. Alexander, David, what do you think?

[David Prieto (frandavid100-gmail)]

Bill, #2 was exactly my thought when I tried the fix. After all the name field is the only field you always need when creating a new task, but one of the least likely to change when editing an existing one.

[Alexander Dietrich (adietrich)]

Bill, I agree with both points, that's how it should behave.

[Alexander Dietrich (adietrich)]

This is now (mostly) fixed in the 2.9.1 release. When editing or creating a task, the cursor blinks in the "Summary" field but the virtual keyboard does not open. The first tap on the "Summary" field then opens the virtual keyboard.

(The following might seem nit-picky...)

There is one minor detail that keeps the behaviour from being perfect: when editing an existing task, the cursor blinks at the end of the summary. When I tap in the field then, the cursor jumps to the beginning of the summary. This seems a bit odd.

Otherwise, thanks for fixing this!