Hi,
Sure, that's the way. The only drawback is a need to use WinDrawBitmap or smth
similar, which implementing speed can't satisfy sometimes.
One strange thing here. Video memory address is determined via processor used,
but all I found is that PalmIIIc has faster processor. Are you sure that it is
actually Motorolla 68328EZ (sorry if mistype) as in previous Palm? If yes, how
could you explain the return of NULL from it's hardware register
(0xFA00)defining video address.
BTW Is here any PalmIIIC owner ready right now to test some of my remakes on a
real hardware? They run well on POSE...
--
Regards,
Konstantin
----------------------
http://klyatskin.da.ru
http://www.bigfoot.com/~klyatskin
mailto:[EMAIL PROTECTED]
> Subject: Re: Writing directly in video memory under OS35
> From: Aaron Ardiri <[EMAIL PROTECTED]>
> Date: Tue, 29 Feb 2000 17:52:22 +0100 (MET)
> X-Message-Number: 37
>
>> I don't know the answer to your question, but I was
>> wondering the same thing myself. I got the code for
>> writing to the display from an article by Edward Keyes
>> (www.daggerware.com), and I'm assuming you're doing
>> the same thing. I downloaded a 3.5 ROM image and
>> tried my appplication on the emulator, and it crashed
>> in the usual way - namely drawing the image to the
>> screen and then crashing. That's all I know.
>
> guys.. you can access the bitmap memory for the screen=20
> just by calling a few API routines.
>
> get the window, then get the bitmap of that window and
> then reference the bits of the 'bitmap' (as done in=20
> burning)
>
> http://www.hig.se/~ardiri/development/palmIII/index.html
>
> the coding is very very simple.. but then again, i guess=20
> you will probably get the warnings on the emu - but you
> are doing it legally :>
>
> az.=20
> --
> Aaron Ardiri=20
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
