On Tue, Jul 01, 2008 at 01:51:50PM +0200, Michal Seliga wrote:
> John Gruenenfelder wrote:
>>
>> Unfortunately, at 308 bytes per item, the index is limited to ~210 total
>> items
>> before the 64K allocation limit is reached.
>>
>
> forget about limit, you can use MemGluePtrNew from glue library with
> which you can allocate more then 64kb in one block and it works from
> palmos 3.5
Thanks for the tip! I guess I should pay more attention to the new functions
added to the glue library. I had no idea there was such an easy workaround.
> or you can use code taken from pdn.palm.com, its setting of some flags,
> it also allows you to allocate more then 64kb in one block
Well, I could at least get some ideas from it. I know the code from the SDK
examples and some of the first code for sane handling of the DIA that appeared
were not compatible with the GPL. Is the code on the PDN different, such as
being public domain?
> and you also can store such big blocks as resources or records in
> databases, problem is that with such databases hotsync will fail so
> backup with hotsync, pilot-tools etc. is not possible
I had considered this, but these indices I am generating are very transient.
For example, as a user browses up/down a VFS directory tree looking for a
document to read, a new index must be generated for each new location. From a
coding standpoint, it's a lot easier to just use an array for this. A lot
faster than using the Dm* functions too, though it's arguable whether a user
would notice it in this particular context.
--
--John Gruenenfelder Research Assistant, UMass Amherst student
Systems Manager, MKS Imaging Technology, LLC.
Try Weasel Reader for PalmOS -- http://weaselreader.org
"This is the most fun I've had without being drenched in the blood
of my enemies!"
--Sam of Sam & Max
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
