> I know that 0x1ffa0000 is likely not going to be a valid address, but
> why is that being returned? It could be that my stack space has been
> exhausted (I don't think so, but maybe). It could be that there's a bug
> with POSE (again, I don't think so).
0x1ffa0000 is a valid address - on some devices, but, not all :)
if you get the address using the code:
ptrScreen = BmpGetBits(WinGetBitmap(WinGetDisplayWindow()));
whatever the above returns is the address of the display directly.
there are other ways to get the display address as well :) but, thats
another excercise for another day *g*
you should not hardcode the value 0x1ffa0000 in your application.
use the series of API calls as above. if you write to the address
returned, it will update the screen. i dont know what area of
ram you were looking at before :) keep in mind that palmos 3.5+
does double buffering. so, it could be 0x1ffa0000 or, another
address (+25600 bytes) :) check out the WinScreenLock() API call
(look at the palmos source code ot get a full insight) :P
you might want to check out the demo's that were submitted to
the MobileWizardry demo competition. the source code to most of
them has been made available; and, they surely do direct screen
access, even the sample i provided (tvstatic) did.
http://www.mobilewizardry.com/
http://www.mobilewizardry.com/board/viewtopic.php?t=103
for the record, POSE does handle direct screen writing correctly.
i have not looked through your entire postings, but, if you have
any questions, zap me a mail personally and i'll answer any simple
questions you have.. your probably just overlooking something.
--
Aaron Ardiri
CEO - CTO
Mobile Wizardry
http://www.mobilewizardry.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
