> > > instead of writing to a database, why not use an unused area of the
> > > display controller? there are a few devices out there that are read/write
> > > and have at least 40-50k free :)
> >
> >It's surely useful to have some comedy with Aaron's quips, but watch this,
> >next question will be "How do I do this?"
>
> The scary part is I'm not sure that Aaron is joking.
Palm IIIc - 80kb of display memory available on the SED 1386 controller.
(if you stuck in 8bpp - you got loads of free space!)
160x160 = 25600 bytes
*2 = 51200 bytes (as palmos has page flipping built in)
this leaves you 30720 bytes on the display controller itself. if you want
to find out how to access is?
UInt32 addr1 = WinScreenLock(...); WinScreenUnlock();
UInt32 addr2 = WinScreenLock(...); WinScreenUnlock();
UInt32 base = MAX(addr1, addr2) + 25600;
i've always seen that page 1 starts at 0 in the display controller
address and the second page follows directly after. of course, it is
very device specific. you could do the same on the Palm V.
i used this trick here:
http://www.mobilewizardry.com/palm/contest/index.php
those were the days :> *sigh*
---
Aaron Ardiri
PalmOS Certified Developer
[EMAIL PROTECTED]
http://www.mobilewizardry.com/members/aaron_ardiri.php
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
