> The Palm OS Window manager assumes that all forms are as wide as the
> screen and bottom justified. (It makes managing the clipping area a
> LOT simpler!)
Bob,
Furthermore, I just found another problem with this calculation of the
clipping area. What happens when the underlying display is *dynamically*
updated and only *partially* obscured? I'm thinking of a clock that ticks, a
map that changes with current GPS coordinates, or displayed data affected by
changes to settings in the dialog just dismissed? I've modified my code to
reset the clip but it seems to me that what's really required is *two*
areas, both the invalidated area and the window clip. This way an
application can modify its draw area (if required) and still be constrained
within the area set for the form. Or have I missed something?
Any chance of nop'ing the full width/bottom aligned messages so I can get my
gremlins to run clean?
Stephen Best
Bitware Australia
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html.
