>So, my real question is, is it possible for WinCreateOffscreenWindow to
>create a window in memory that ends up being larger than 64K? I'd be
>really surprised if it just created the largest possible window, didn't
>update the window bounds, and didn't return any errors.
I just looked at the 3.2 sources, and if it can't allocate the display
buffer for the window, it just cleans up and returns zero. And no, it
doesn't support allocating something >64k, but since the offscreen window
is always 1-bit, it'd have to be a pretty large window to go past that. So
it sounds like WinCreateOffscreenWindow has done what you asked,
successfully. (You could always look at the struct in the debugger to
verify.)
Oh, wait, the multiply code doesn't cast the intermediate stuff to a 32-bit
integer, so perhaps it is just losing track of the fact that you're asking
for >64k since it is just multiplying two shorts and dropping the overflow.
(I haven't looked at the disassembly to verify.)
In any case, it can't handle allocating >64k, even if there wasn't an
overflow problem, so don't ask it to :-)
-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/
