The new beeping sounds do indeed appear to be a new bug. I’ve got a potential fix, so hopefully that will be available at some point on Monday.
I think the ‘preferences’ menu is actually working as intended now. The menu returned from MenuModel::createAppleMenu has isEnabled set to false on the “Preferences…” item. Previously, items in the main menu did not respect their enablement state, which is why the item appeared to be enabled (it should have been displaying as disabled).
To make this work as you expect, the PopupMenu will need to be tweaked so that its items have their isEnabled members set appropriately. At the moment, isEnabled is set to false because the menu is initially created at a point where the BipComponent (which handles the preferences command) is not a viable target component.
Here are some ideas:
- Iterate the PopupMenu after creating it and set
isEnableddirectly to true for any items that you really want to be enabled. - You could postpone creating/setting the main menu items until after the
BipComponenthas become visible and grabbed keyboard focus. - Change the target of the “Preferences…” command so that the target is definitely viable at the point where the menu is created. This might mean overriding the ApplicationCommandTarget functions directly on BipApplication to handle preferences there.