I did not look into the update, but if you reported all differences
correctly, then it is a disappointment for me. They simply ignored known
bugs.
> I know when my application as all its databases closed but is it possible
> that another application still got an opened database while my application
> is running???
E.g. standard PIM databases. Any background app may do the same. Some of
them really do and they even modify them while the foreground app is
running.
Regards,
Jan Slodicka
----- Original Message -----
From: "Regis St-Gelais" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[email protected]>
Sent: Friday, April 01, 2005 6:34 PM
Subject: Updated NVFS_White_Paper.doc on PalmOne web site
> PalmOne as updated its NVFS_White_Paper.doc
> Don't ask me when. There is no version number or revision date on the
paper.
>
> At first glance, that added item 9 and 10
>
> 9- DmSyncDatabase
> There is a bug in the DmSyncDatabase.
>
> The return value of the DmSyncDatabase is being put in A0 instead of D0
>
> (i.e. the return value is treated as a pointer instead of a int value).
>
> Developers can use the following workaround:
>
> <snip>
>
>
>
> 10- MemHeapCompact crash on Tungsten T5
> MemHeapCompact causes the Tungsten T5 to crash when there are open
> databases.
>
> MemHeapCompact works fine when there are no open databases.
>
> Please make sure to close all databases before calling MemHeapCompact.
>
>
>
> My question is:
> I know when my application as all its databases closed but is it possible
> that another application still got an opened database while my application
> is running???
>
> If yes, how can I know when its safe to call MemHeapCompact?
>
>
>
> --
> Regis St-Gelais
> www.laubrass.com
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
