>From the PilRC manual page, in the Known Bugs section:
FIELD
MAXCHARS required for field control to accept characters to work.
You shouldn't need to handle anything beyond that on your own, but your
event loop does need to pass all events you don't specifically handle to
SysHandleEvent, and it will deal with all the nitty gritty of text input for
you. You don't need to allocate or provide a buffer for the field, and the
field control can automatically request resizes of its memory handle when it
needs more, but it will never allow more than MAXCHARS. Hope this helps.
-Thomee Wright-
"John Prinos" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Hello all,
>
> I'm writing the code for the last form for my application. I'm testing
> it on pose.
>
> It consists of a field, which takes up nearly the entire form and a
> "done" button. All I want to do is take some text input from the user
> and store it someplace.
>
> Through pilrc, I set the following attributes for the field:
>
> FIELD ID 5001 AT (4 16 152 124) USABLE EDITABLE DYNAMICSIZE UNDERLINED
> MULTIPLELINES HASSCROLLBAR
>
>
> When the form pops up, I can see the field because of the underlines and
> I can manually set its focus.
>
> Now, here's the problem: When I try to type text into it, or use
> graffiti or the palm keyboard, all I get is beeps with no text showing
> up. What needs to be done to be able to get text to show up? According
> to the 'dummies' book, the system allocates memory itself, so little
> needs to be done by the programmer.
>
> I've looked around for examples as to how to get text entered into a
> field. Is it supposed to happen automagically or do I have to be VERY
> explicit in the forms event handler? There seems to be nothing stated
> explicitly as to how this is to be done.
>
> Any help would be appreciated.
>
> John
>
>
>
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
