>What exactly does the API routine WinSetWindowBounds(WinHandle,
>Rectangle) really do?
In 3.5, it validates the window handle, makes sure that the window is
visible (if not it returns, and on a debug rom displays a msg), copies the
bounds into the window's structure, and resets the clipping region just in
case. In older OS versions it didn't even reset the clipping region.
That's it. If you wanted to change the allocated size of the underlying
storage of an offscreen window, this isn't the way. If you're trying to
move it on the screen, this doesn't cause any redrawing to happen so you'll
need to do that. In other words, there aren't any side effects other than
resetting clipping: it just updates an internal structure with the new
bounds.
The docs are "spartan" in this case because the routine's operation is
rather spartan :-)
As for what other routines in the OS use the window's bounds and how, well,
that's a long essay question!
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
