Alltime Data Entry

[DavidK]

I have been using Alltime 4.06 for several months. Recently, I replaced my Palm515 with a Palm Tungsten E with Palm OS 5.2.1 and Graffiti 2.

The Alltime data validation does not work properly on the Tungsten when I write in the entry screen. The error is associated with any 2 stroke graffitti character.

For example, when I write "A" in the Client entry box, Alltime looks up the first client beginning with "A" as it should. If I then write "T" as the second letter in the Client entry box, Alltime then responds with the first client beginning with "T" rather than the first client in the validation list beginning with "AT". This only happens when the second letter is a graffiti double stroke letter " i, t, k". It also works fine when I use the palm keyboard rather than graffiti to enter the client name.

The problem is present in all data entry fields, not just the Client field.

Has anyone else had and solved this problem? Are there preference or settings which can fix it?

Thanks
Dave

[kfroberts]

David: I have the same problem with my Palm Zire 71. This bug wasn't present in versiin 3 of the program. You may also notice that if you have a lot of client entries, only half of them show up in the validation lists. I've searched for an answer extensively, but haven't found one yet. I have emailed Iambic support now three times asking for a fix or a clarification and they have not yet deigned to honour me with a reply. As soon as they do, I'll post their fix or thier excuse.

[adriano]

Hi All,

the issue you are reporting is related to the multistroke system used by graffiti2. The problem afflicts all the data entry fields that support quickfill. I.e. all the data entry fields that automatically complete the entry by looking it up in the validation lists.

kfroberts, I believe that the problem for you was not present in V3 because you were using Alltime 3 on a device that didn't have graffiti2, but the "old" graffiti.

Please note that this problem is present in the builtin applications themselves (try to use quickfill in the "city" or "state" edit fields of the contacts app for example).

We are working on a possible solution, which we'll plug in all our application featuring quickfill (including Agendus).

- Adriano