Scott Johnson wrote:
>
> No, can't assume that. Let's say the app must be a well behaved citizen
> on the organizer -- it must coexist with other apps, can't redefine the
> hard buttons, can't interfere with HotSync, can't disable the
> Applications Launcher, doesn't have anything special connected to the
> serial port, etc. So whatever is needed to enforce this required
> field(s) constraint, must happen via "normal" user interface.
Then, in a hypothetical sense, I would still "interfere" with
HotSync's in the following manner: don't HotSync Zip-less records
(of course). But every time the program starts, inform the user
of any existing Zip-less records that need to be completed, as in
"There are 7 unfinished records (need Zip Code). Would you like
to complete them now? | Yes | No |"
Other than that, the user would be free to use the rest of the
organizer and also use the (hypothetical) census program without
restrictions. I don't think this is the best method, but it may be
one of the closest to the zen-of-palm solutions given your (amazingly
difficult) scenario. (Smart bombs take out conduit source code?! ;)
-Daniel.
