On Friday 07 May 2004 03:37 am, Ben Combee wrote: > I don't see anything in the code of Palm OS 5.4 that would cause the chunk > you assign as the appInfo block to be locked. Can you provide sample code > that shows this bug?
Thanks for checking. I will post a full example as soon as I can. Sorry for the confusing pseudo below. Basically I did: .. create new file DmGetDatabaseLockState() /* get highest,count,busy */ .. print values DmNewHandle() /* create appinfo */ DmWrite() /* copy stuff to it */ MemHandleUnlock() /* unlock the appinfo */ MemHandleToLocalID() /* prepare for assignment */ DmSetDatabaseInfo() /* assign appinfo */ /* placeholder */ DmGetDatabaseLockState() .. print values The "print values" before showed highest=0,count=0,busy=0. The "print values" after showed highest=1,count=1,busy=0. No records in database. If I used NULL for the appinfoID parameter of DmSetDatabaseInfo() then it was highest=0,count=0,busy=0. Also if I do this: MemLocalIDToGlobal() /* the appinfo parameter above */ if (MemHandleLockCount()) MemHandleUnlock() .. at /* placeholder */ it will show highest=0,count=0,busy=0 so I know it is the appinfo. Was using OS 5.3 simulator both debug & release. I will do some more experiments and provide a better example as soon as I can. -- /* Chris Faherty <[EMAIL PROTECTED]> */ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
