>The sysAppLaunchCmdFind Parameter block doesn't have any member to pass a
>database ID.
There's two problems with the find code. This is one of them. The other is
that the record's unique ID really needs to be passed. If anyone has good ideas
on how to fix these two issues without breaking existing apps, I'm all ears.
>I am thinking of using a feature to store the current database ID.
This is the best solution to my knowledge.
>You can use the upper few bits of the record number to indicate which of
>your databases is current
Hmmm. This probably happens to work today. But do folks really want to go
around writing software which happens to work? What happens when Palm extends
the size of Unique IDs to 32 bits? Will users be understanding when their
software no longer works? A feature should always work and the technique can be
dropped when a good one is available.
>While we are at it, is there any equivalent function for EvtSysEventAvail
>in Palm OS 1?
No. That's why we added it! Just omit that feature when running under Palm OS
1.x.
-Roger Flores
