Suspect Anomaly-<End> disabled by CapsOff

[armsys]

Probably starting from v10, I started to notice that on my keyboard was disabled. After months of troubleshootting, today I discover the exact cause is CapsOff. CapsOff has never been suspected as the probable cause because all the scripts have been working fine under previous versions of Macro Scheduler in the past.
Today, as an experiment, I comment out all CapsOff. The is now responsive and behaves predictably.
In those days without key, my editing jobs were excruciating and frustrating.
Can you confirm and verify my anomaly discovery?
Thanks.

[evangelmike]

Greetings! I have at least 16 Macro Scheduler macros which use the CapsOff instruction and the End key works just fine on my keyboard.

[armsys]

I could be wrong. If it's the case, other MS users could have raised the issue before. That's why I seek other MS users' verification. My keyboard is Dell SK-8135. Many thanks for your response.

[JRL]

I tested with the following.

Capsoff
Mdl>Done

I had notepad open with a test sentence, the end key worked fine. I tried this with the capslock on and with the capslock off. I tried with the script still active and with the script completed.

Perhaps there is something more to your script that is a factor.

[Me_again]

Maybe you could post a simple test macro to demonstrate the problem?

[armsys]

Hi Me_Again, JRL, and evangelmike,
In this case, definitely my initial observation was reckless and faulty. The intermittency of disabled End key misled me to suspect MS. Hours later the disable End issue resurfaced. Because all CapsOff statements have already been deleted, it could not possibly caused by MS.
Thanks for your help.