OK, so Carbon was designed with the smart feature to provide localized standard
application menu items,
whereas Cocoa app always are stuck with the menu from the .xib file.
The Carbon approach is much better, e.g. to accommodate new application menu
items from Apple,
Cocoa developers has to
> On Aug 22, 2018, at 5:19 PM, Lars C. Hassing wrote:
>
> Thanks, but I would like to avoid an .xib file.
> However, like you suggested I have created a new Cocoa app in Xcode, and I
> look at its content as a basis for creating the menubar programmatically.
>
> Still, this doesn’t doesn’t
You should use a .xib instead of creating the menu bar programatically. Create
a new Cocoa App in Xcode and it will have all of what you seek pre-configured
in a .xib with no code needed.
—Rob
> On Aug 22, 2018, at 2:14 PM, Lars C. Hassing wrote:
>
> In decarbonizing I have now come to
In decarbonizing I have now come to creating a menubar programmatically using
NSMenu.
Carbon seems to be so nice to add standard items to the application menu:
Services, Hide app, Hide Others, Show All, Quit app,
and they are added using the user’s Preferred Language setting in System
