Background:
We have a data item (the default calendar in our multiple calendar
application, wsCalendars) that is, by default, given the same name as the
palm's user name the very first time the application runs. If there is no
user name set on the palm, or if we cannot access it, we name the calendar
"Default". Additionally, we save information about each calendar, including
its name, on the desktop (amongst, possibly, other places).
If the user:
1. hard resets his/her palm,
2. syncs at his/her desktop, and
3. choses to restore to his/her existing user name.
our wsCalendar application is restored to the palm, then our conduit runs.
The first task of our conduit is to make a remote call to our application
for the app to prepare data on the palm. The first thing the app does,
since it has no data, is to recreate a default calendar. Unfortunately, it
appears that the palm does not know, AT THIS TIME, what its (soon-to-be)
restored user name is, so this calendar gets called "Default". This causes
an undesirable conflict during the syncrhonization.
Question:
When, during a restore sync, is the user name saved into its normal place as
a psys resource (sysResIDlkUserInfo)? Is it available from anywhere else
during this sync??
Note:
We do not set the backup bit on our data files in order to keep the (already
substantial) sync times down, so this solution is not available/desired.
-robert mckenzie
<[EMAIL PROTECTED]>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
