1st character entry that zooms into text field

Hi Clayton,

We have been using a pre-compile option for CommCare that “zooms” into the
text fields (rather than entering text inline) so that the phone can support
writing in different scripts (i.e. Hindi). The language support is working
well, but text entry is now much slower. Entering a single character now
requires 4 keypresses:

  1. To “zoom” into the field, you first press a button on the keypad, but
    this button is not registered. This button cannot be the center “OK” button,
    though, because that moves it on the next question.
  2. You then enter in your text
  3. You click the center “OK” button to “zoom out”
  4. You click the center “OK” button again to move to the next question

The fact that the first keypress must be a character but that it is not
entered into the field is somewhat inconvenient and also pretty confusing
until you get used to it. Even then, this behavior is not consistent with
the normal text entry style, so after a couple weeks of it, I still mess up
text entry rather frequently.

Is it possible to catch the first keypress that triggers the “zoom” behavior
and programmatically enter it into the field?

Thanks
Jon

Unfortunately the behavior of the “zoom-out” text entry is entirely out of
our hands. The behavior you’ve outlined here is the default behavior for
text input on Nokia phones, which is cumbersome and awkward. This is why
we’ve been using the Polish interface instead on our builds. I’ll
investigate a bit deeper whether there’s any way to get the full character
supported we want for Hindi character input in Polish, but I can’t guarantee
that it’ll work or that it’ll be as complete.

-Clayton

··· On Mon, Dec 13, 2010 at 11:37 AM, Jonathan Payne wrote:

Hi Clayton,

We have been using a pre-compile option for CommCare that “zooms” into the
text fields (rather than entering text inline) so that the phone can support
writing in different scripts (i.e. Hindi). The language support is working
well, but text entry is now much slower. Entering a single character now
requires 4 keypresses:

  1. To “zoom” into the field, you first press a button on the keypad, but
    this button is not registered. This button cannot be the center “OK” button,
    though, because that moves it on the next question.
  2. You then enter in your text
  3. You click the center “OK” button to “zoom out”
  4. You click the center “OK” button again to move to the next question

The fact that the first keypress must be a character but that it is not
entered into the field is somewhat inconvenient and also pretty confusing
until you get used to it. Even then, this behavior is not consistent with
the normal text entry style, so after a couple weeks of it, I still mess up
text entry rather frequently.

Is it possible to catch the first keypress that triggers the "zoom"
behavior and programmatically enter it into the field?

Thanks
Jon

I reviewed the docs again, and it does look like Devanagari input with the
Direct Input (no popout) isn’t really possible without writing it from
scratch, which is extremely impractical, so unfortunately Hindi text input
is probably at the mercy of the Nokia interface.

-Clayton

··· On Mon, Dec 13, 2010 at 11:07 AM, Clayton Sims wrote:

Unfortunately the behavior of the “zoom-out” text entry is entirely out of
our hands. The behavior you’ve outlined here is the default behavior for
text input on Nokia phones, which is cumbersome and awkward. This is why
we’ve been using the Polish interface instead on our builds. I’ll
investigate a bit deeper whether there’s any way to get the full character
supported we want for Hindi character input in Polish, but I can’t guarantee
that it’ll work or that it’ll be as complete.

-Clayton

On Mon, Dec 13, 2010 at 11:37 AM, Jonathan Payne paynejd@gmail.comwrote:

Hi Clayton,

We have been using a pre-compile option for CommCare that “zooms” into the
text fields (rather than entering text inline) so that the phone can support
writing in different scripts (i.e. Hindi). The language support is working
well, but text entry is now much slower. Entering a single character now
requires 4 keypresses:

  1. To “zoom” into the field, you first press a button on the keypad, but
    this button is not registered. This button cannot be the center “OK” button,
    though, because that moves it on the next question.
  2. You then enter in your text
  3. You click the center “OK” button to “zoom out”
  4. You click the center “OK” button again to move to the next question

The fact that the first keypress must be a character but that it is not
entered into the field is somewhat inconvenient and also pretty confusing
until you get used to it. Even then, this behavior is not consistent with
the normal text entry style, so after a couple weeks of it, I still mess up
text entry rather frequently.

Is it possible to catch the first keypress that triggers the "zoom"
behavior and programmatically enter it into the field?

Thanks
Jon

bummer. thanks for checking.

-jon

··· On Mon, Dec 13, 2010 at 12:35 PM, Clayton Sims wrote:

I reviewed the docs again, and it does look like Devanagari input with the
Direct Input (no popout) isn’t really possible without writing it from
scratch, which is extremely impractical, so unfortunately Hindi text input
is probably at the mercy of the Nokia interface.

-Clayton

On Mon, Dec 13, 2010 at 11:07 AM, Clayton Sims csims@dimagi.com wrote:

Unfortunately the behavior of the “zoom-out” text entry is entirely out of
our hands. The behavior you’ve outlined here is the default behavior for
text input on Nokia phones, which is cumbersome and awkward. This is why
we’ve been using the Polish interface instead on our builds. I’ll
investigate a bit deeper whether there’s any way to get the full character
supported we want for Hindi character input in Polish, but I can’t guarantee
that it’ll work or that it’ll be as complete.

-Clayton

On Mon, Dec 13, 2010 at 11:37 AM, Jonathan Payne paynejd@gmail.comwrote:

Hi Clayton,

We have been using a pre-compile option for CommCare that “zooms” into
the text fields (rather than entering text inline) so that the phone can
support writing in different scripts (i.e. Hindi). The language support is
working well, but text entry is now much slower. Entering a single character
now requires 4 keypresses:

  1. To “zoom” into the field, you first press a button on the keypad, but
    this button is not registered. This button cannot be the center “OK” button,
    though, because that moves it on the next question.
  2. You then enter in your text
  3. You click the center “OK” button to “zoom out”
  4. You click the center “OK” button again to move to the next question

The fact that the first keypress must be a character but that it is not
entered into the field is somewhat inconvenient and also pretty confusing
until you get used to it. Even then, this behavior is not consistent with
the normal text entry style, so after a couple weeks of it, I still mess up
text entry rather frequently.

Is it possible to catch the first keypress that triggers the "zoom"
behavior and programmatically enter it into the field?

Thanks
Jon