Bernie wrote: > I'm using the carbon command event _kEventCommandUpdateStatus to > fix my menus. > > In this shortened example, there are three menus (Window, Arrange, > Options). If I use keyboard commands to select the item in the > Window menu (cmd-K) or the Options menu (cmd-Y), > _kEventCommandUpdateStatus gets called to update the Arrange menu. > If I remove the hierachical menu from the Arrange menu it works as > expected. > > Can anyone show me what I'm doing wrong? Can you describe more clearly what is not working? (1) What you did to provoke the unexpected behaviour (2) What you expected to see (3) What you actually saw. FYI, Tiger made some obscure-seeming but possibly relevant changes in kEventClassCommand handling: "Event routing for kEventClassCommand events sent to menus has changed. Previously, a command event (either UpdateStatus or Process) that was not handled by a menu would next be sent to the focused control in the user focus window. Events are now routed to the menu's parent menu (including the root menu, for menus that are inserted in the menubar). Only after the event has been sent to a menu that has no parent, which effectively means that it has reached either the root menu or the root of a popup menu hierarchy, is the event propagated to the user focus target." Robert P.