I had a working form with a couple of input fields in it. I needed to add
more UI objects to the form, but since there was no more room, I decided to
partition the form into multiple "pages". What I did was to put a one-row,
three-column table at the top of the form to be used to move to the
different pages (tap in column one, page one displays, etc.), and then put
down the page one UI objects on the empty form, the page two objects on top
of the page one objects, and the page three objects on top of the page two
objects. In the code, I made a tap in column one of the "page" table do a
FrmHideObject on all the objects in pages two and three, and a FrmShowObject
on all the objects in page one (and similarly for the other two pages).
There was a wrinkle on this for the table object on page three, since
FrmHideObject doesn't seem to hide tables, but this is the gist of it.
This resulted in a messy looking form in Constructor, but it worked just
fine ... with one exception. The input fields now will not accept any pen
input, even though they allow the focus to be put there by the pen, and they
allow input via the keyboard that comes up when one taps on the relevant
spot in the Graffiti area. I've tried everything I can think of to get this
to work, but to no avail. Since these fields work fine when cut and pasted
to a less complex form, I suspect I've hit some kind of limit on the number
of UI objects per form. There are 41 objects on the form, almost all of
which are popups consisting of a label, a popup trigger, and a corresponding
list.
Have I hit a real limit here? Is there something about this setup I'm not
seeing that could cause the fields not to accept input? Is this a
reasonable way, in general, to partition forms? Have any suggestions as to
how to make this work?
Thanks,
Mark Peters
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
