(If you open the Keyboard pane of System Preferences, you can see what's there.) This is also pretty simple, but it's next to useless in modern OS X, because only global shortcuts usually get registered. Look at the shortcuts the app registers with the OS.This is pretty simple, but only handles menus created from the NIB. Look at the NIB files embedded in the app.These are found in Carbon/Menus.h they're more fiddly, and have much less of a future, but at present they'll work for both Carbon and Cocoa apps.Insert your own code into every app and use the Carbon Menu Manager APIs in HIToolbox.Then you can translate what you've learned into the language of your choice. If you're interested in this one, inject fscript into an app and start playing with the object browser and scripting interface, and you should be able to figure it out from there.The downside is that it doesn't work on Carbon apps, but there are fewer of those left every day. ![]() In some cases, this can even get you dynamically-generated menu items that don't currently exist but could.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |