> On Nov 25, 2019, at 1:26 AM, Allan Odgaard via Cocoa-dev
> wrote:
>
> On 25 Nov 2019, at 7:36, Kurt Bigler via Cocoa-dev wrote:
>
>>> With a menu delegate you can lazily update the menu (menuNeedsUpdate:) or
>>> you can even bypass updating the menu for key events by implementing
>>> menu
On 25 Nov 2019, at 7:36, Kurt Bigler via Cocoa-dev wrote:
With a menu delegate you can lazily update the menu
(menuNeedsUpdate:) or you can even bypass updating the menu for key
events by implementing menuHasKeyEquivalent:forEvent:target:action:.
I'm not sure that's relevant to my situation,
On 11/24/19 1:37:17 PM, Allan Odgaard via Cocoa-dev wrote:
On 24 Nov 2019, at 22:28, Kurt Bigler via Cocoa-dev wrote:
[…] The idea for least inefficiency given the global updating pass is to defer
(akin to lazy evaluation) the actual menu item updating until the last
possible moment. The last
On 24 Nov 2019, at 22:28, Kurt Bigler via Cocoa-dev wrote:
[…] The idea for least inefficiency given the global updating pass
is to defer (akin to lazy evaluation) the actual menu item updating
until the last possible moment. The last possible moment for mouse
access is when the user clicks i
I have an app in final stages of conversion from Carbon to Cocoa. It uses a
legacy architecture for menu item enabling that originated with the Think Class
Library. It is not really practical to consider redoing the entire
implementation so I am retrofitting it. The method used is to make a p
