ying to re-implement Carbon's "enable/setup menus just before key
equivalents are processed" behavior which worked so well for us (since OS 7)
using WaitNextEvent(), but using Cocoa.
I wouldn't care if the solution required OS X 10.10.99.
--Jim
============
On Mar 18, 2014, at 7:45 AM, Kyle Sluder wrote:
> On Mar 13, 2014, at 1:19 PM, Jim Prouty wrote:
>>
>> We'd love to have menuNeedsUpdate: be called before Cocoa starts calling
>> menuHasKeyEquivalent:forEvent:target:action:.
>
> Why can't you just d
Our app allows the user to write programs and to create custom menus and menu
items, including setting key equivalents.
Because the key equivalents are under user control and because we re-use some
for multiple purposes, menu items' key equivalents change a lot.
We need to get a chance to updat
Our app allows the user to write programs and to create custom menus and menu
items, including setting key equivalents.
Because the key equivalents are under user control and because we re-use some
for multiple purposes, menu items' key equivalents change a lot.
We need to get a chance to updat
