> Is this possible?

Yes, I think so.

> Do I have to have two different forms?

No, I don't think so (based on your description).

> What can I do?

Code it? ;-)

Where exactly is your problem? I implemented a
numeric keypad (not an entire keyboard) a while
ago, and simply used buttons. You may have to
do something more fancy. Basically, when you get
the event that the user has selected a key (in my
case it was a button (ctlSelectEvent) event), you
need to act upon it. If your "main" field is
display only, handle the update to your 'entry'
yourself. If your main field is also enterable
via Grafitti etc., look into simulating the entry
of a character by enqueueing the appropriate
event/character using EvtEnqueueKey.

Based on previous posts from you a couple days
ago, I seem to remember that you're trying to
use this custom keyboard approach because your
app was having problems dealing with events to
begin with. Might be better to sort those
problems out first and then use the built-in
keyboard if that's appropriate for your application.
____________________________________________________________

I have fixed the problem that was crashing the palm, but the system virtual
keyboard is still not my best option.  Some handshaking is involved when my
application starts, and if the user accesses the system virtual keyboard for
an extended period of time, I have to repeat the handshaking.  Not sure why
this is happening, but it doesn't matter.  (When I have more time, I will
determine why this is happening.  Until then, I need to find some middle
ground.  It is not acceptable to have the only input as Graffiti.)  The
system virtual keyboard covers practically the entire screen, which is not
what I want.  What I really want to know is how to handle opening the forms,
from then I know how to process the events.  My 'Main' form is full of UI
objects (fields, lists, labels, etc.).  Only one of the fields accepts user
input, however.  This is the field that I would like to remain visible.
Should the keyboard be created (using Constructor) ontop of all these other
UI objects and just become visible when the user would like to use it, or is
there a better way to do it.  I'm new to Palm, so I'm not really sure what
the best method to do this is.

Thanx for all your help!


-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to