excel Debug causes loss of CMD key

[MHMac]

Hi,
the facts - Excel for Mac 2024 V16.95.4 - Macos Sequoia 15.3.2 - MacBook Pro with M4 pro - 48Gb Memory
The problem ...
I'm working with excel macros (which are quite complex) and have been experiencing a problem with "key mapping" around the CMD key.
In Excel Debug - happily stepping into and over subs (CMD-SHFT-I or CMD-SHFT-O). After a little while (not preceise or similar times) I will press CSI/CSO and all I get is the letter "I" or "O".
At this point if I switch to anything else (Textedit for example) and try and use the CMD key - CMD-C for CMD-V for example - all I get is the character (C or V) and not the function.
Basically - the CMD key no longer works.

I have only one keyboard mapping different from standard Sequoia - Screenshot is now Shift-F15 (avoids a key which I keep hitting by mistake).
The partial resolutions ....
a) If I am "lucky" it is just shut down excel (and quit) and then restart.
b) Otherwise it is completely restart the MacBook.
(a) is a pain especially if I have quite a few "Watches" in the debug window - all have to be setup again.
(b) is just totally Waaaaaaaaaahhhhh !!!

Has anybody else seen this behaviour ?
Does anyone have a permenant solution or pointers ?
Anything else I can check to determine the root cause ?

I've only recently moved from Win to MacOS and I am not thrilled by the idea that I will have to maintain a Windows machine just to edit excel or that I have to put a Parallels VM on my MacBook for the same purpose.

Any and all comments gratefully received,
cheers

Mike.

 

[Raz0rEdge]

One thing I will say right out of the bat is the Excel definitely performs poorly with scripting on Mac than it does on Windows. The port isn't accurate.

That being said. The fact that the CMD key disappears in other native Mac apps is interesting.

Does the CMD key disappear while only using Apple apps or when Excel is in the picture?

 

[MHMac]

hi Ashwin,
thanks for reply.
I agree - the port is very poor - many other negative comments - but enough for now !

I've only experienced this in Excel - and never seen it just with Apple apps.
I've tried debug in Word (again up to date for Mac) and it doesn't seem to break - but maybe not the same level of complexity as the excel code.

It really is strange.
One thing new is that I tried setting key mappings back to default - CMD key was still ineffective.

Any more thoughts ?

Mike.

 

[Raz0rEdge]

I don't have Excel installed, but other debuggers I've used trend to use either F5, F6 or F10, F11 for the stepping command.

I can't think of any reason why a particular command would stop with constant use. It's almost like the CMD key keypress is being consumed by some application and not propagating through the rest of the system.