Ran into the following annoying flaw in the Palm OS Table element (still in OS 3.5). If you dynamically resize a table by resetting the bounds of the table itself, everything works perfectly with just one, annoying flaw: if you tap on a field which has a number of lines larger than the number of lines currently displayable in the table AND when the table has to be scrolled, the Palm OS, when it goes into 'edit mode', simply draws all the lines of the field, drawing below the bottom bound of the table. There are no other problems - even trying to limit the number of lines in the table does not work, as it appears that the field edit routines simply obey the maximum number of displayable lines in a field (currently def'd at 11) and ignores the table boundary. If you first scroll the table so the long entry is at the top of the table and THEN tap on the field to go into edit mode, it's drawn and clipped properly - it's only when the table scrolls to position the long entry on the first line of the table, that it goes beserk and overdraws the screen. I did finally find a complex workaround for Datebk4 (this is part of the reason I'm a bit behind releasing Datebk4 as this particular problem was something I only noticed a few days ago). Seems this should be fixed, no? ____ ____ / ___) / ___) ( (___ ( (___ \____)heers! \____)ESD Pimlico Software, Inc. Home of DateBk3 and WeekView: http://www.gorilla-haven.org/pimlico The Dewar Wildlife Trust, Inc. Home of Gorilla Haven: http://www.gorilla-haven.org . . . . . . -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palm.com/devzone/mailinglists.html
