I tried again after a few time and indeed it works -keydown: in the view does work indeed with your solution however I did simplify to illustrate the issue. My initial program uses -moveRight: and moveLeft: in the viewController to test both combined keys option and arrows. When using the combination, the option is never detected. I will issue a new request for it

I change using your solution and it does not work

Hello Richard Indeed the -keyDown: method/func is called in all cases, but fails only in Obj-C macOS 12.7.6 Thank you Jean

And the issue comes back after a restart … Regards Jean

I have followed your method and I can compile but it does not show the expected result (using NIB) I have to wait for the correct fix Regards Jean

Nope, I have filed the issue to the Feedback Assistant (FB20481818) and I am waiting for the resolution Regards Jean

Were you able to follow up the issue to the right team?

Thank you for your feedback. Here is the number of the Feedback Assistant I filed: FB20481818. It contains a little project to illustrate the issue. Unfortunately, the project is based on an AudioUnit using AudioUnitRender callback but this induces another issue returning -10863:kAudioUnitErr_CannotDoInCurrentContext at each frame. I did file another Feedback Assistant for that (FB20406343)

I'm using an Intel MacBook Pro version 12.7.5 therefore NavigationSplitView is not available

I just tried contentShape and frame suggested on the current test, but the 2 issues remain. I will try the navigation split view.

I tried but the swap has no impact on the CPU usage and the result is not the one expected as it will fill all ranges in arrMag that are above the expected  one. When I fix this issue using a labeled-statement, the CPU usage remains high

I just did but the swap has no impact on the CPU usage and the result is not the one expected as it will fill all ranges in arrMag that are above the expected one. When I fix this issue using a labeled-statement, the CPU usage remains high

I just did but the swap has no impact on the CPU usage and the result is not the one expected as it will fill all ranges in arrMag that are above the expected one. When I fix this issue using a labeled-statement, the CPU usage remains high

I just did but the swap has no impact on the CPU usage and the result is not the one expected as it will fill all ranges in arrMag that are above the expected one. When I fix this issue using a labeled-statement, the CPU usage remains high

I just tried but it does not provide the expected result ( all range above the expected are filled) and the CPU usage remains high. I tried using a labeled-statement to fix the result but no real impact on the CPU