At 1:40 PM -0800 11/17/99, Ken Krugler wrote:
>If the command ids of the standard edit items matches what's defined in UIResources.h
>(file name from the 3.5 SDK), then the system will automatically handle these
>commands for you. The defined set is:
>
>#define sysEditMenuUndoCmd 10000
><snip>
In Palm OS 3.5, choosing Undo from the command bar generates a menuEvent with ID
10000, even if your application includes its own Edit menu resource with an ID other
than 10000. This is another reason to use the standard Edit menu rather than rolling
your own. If you need custom behavior, you can always handle the menuEvents yourself
and set handled=true if you want to prevent FrmDispatchEvent from processing the
events. For example, the ToDo List application handles the paste menuEvent, creating a
new record before allowing the menuEvent to be processed by FrmDispatchEvent.
I would recommend that the 3.5 documentation stress the need for applications to use
the standard Edit menu (10000) in their menu bar resources. The tutorial should be
changed to use the standard Edit menu as well. I would also recommend that developers
switch to using the standard Edit menu if they're not already doing so, to ensure
compatibility with Palm OS 3.5.
I have two questions:
1. The source for the PIM apps provided with the 3.0 SDK include Edit menu resources
with IDs different than 10000, and yet their menuEvent handlers look for the standard
Edit menu item IDs (10000, etc). Anyone know what's going on here?
2. What are the rules for using the standard Edit menu? Can we add our own items on
the end? If we do so, are we risking compatibility problems with future versions of
the OS or with the Japanese versions?
-
Danny Epstein, Applied Thought Corporation
Have friends with Palm organizers? Get BeamBooks!
http://www.appliedthought.com/beambooks
