On Wed, Oct 15, 2003 at 04:19:15PM -0500, Hildinger, Robert wrote: > "Dave Carrigan" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> > I'm having a strange issue with the dynamic input area on the T|3. > I don't believe this is expected behavior - it should be fixable. After ripping apart the example code, I finally determined that the problem was caused because I wasn't calling PINSetInputAreaState. I was taking the documentation for PINSetInputAreaState at its word where it said "Most forms should not set a state for the input area". What this actually means in Palm documentation speak is that you actually must call PINSetInputAreaState, but pass it a parameter of pinInputAreaUser. Neglecting to call it at all results in the behavior I was seeing. I should have realized that the documentation would be misleading. I spent most of yesterday trying to figure out why my form wouldn't change size, because nowhere in the entire documentation does it say that you explicitly need to change the form's size with WinSetBounds when you get the winDisplayChangedEvent. Why should I have expected anything better in any other part of the api docs? Thanks. -- Dave Carrigan Seattle, WA, USA [EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680 UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL Dave is currently listening to The Fall - Cab It Up! (I Am Kurious Oranj) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
