About "SetCapsLockState AlwaysOff" and combination of CapsLock.

[dsewq1LYJ]

It is pretty useful in Vim when you call the

Code: Select all

SetCapsLockState, AlwaysOff

but here comes the problem, after the call any Combinations from CapsLock stop working.

e.g.

Code: Select all

SetCapsLockState, AlwaysOff
CapsLock & Space::foo()

You can not trigger the foo() by press down CapsLock AND Space.
Uh...how to fix this issue ?

[Nextron]

Your example works for me..?

[dsewq1LYJ]

Your example works for me..?

Sorry my bad.

Call [ A.ahk ]

Code: Select all

SetCapsLockState AlwaysOff

in A.Ahk

[ B.ahk ]
and press follow hotkey in different script file.

Code: Select all

CapsLock & Space::foo()

then you can not trigger the foo().

[Nextron]

For me it is only blocked if SetCapsLockState AlwaysOff is called after the hotkey script. This could mean that SetCapsLockState AlwaysOff works by setting the state and then using the keyboard hook to drop all key presses. Any other non-admin hooks loaded before it wouldn't see the events either, those loaded after it or hotkeys using the same hook (same script) would.

[dsewq1LYJ]

For me it is only blocked if SetCapsLockState AlwaysOff is called after the hotkey script. This could mean that SetCapsLockState AlwaysOff works by setting the state and then using the keyboard hook to drop all key presses. Any other non-admin hooks loaded before it wouldn't see the events either, those loaded after it or hotkeys using the same hook (same script) would.

Should I combine those two scripts ?

Could it affect the performance of my Script ?

[Nextron]

I prefer to combine scripts as much as possible. Whether performance is impacted greatly depends on your use-case. I think that unless your doing really time sensitive things or interacting with the AHK process itself, you're pretty safe.

[dsewq1LYJ]

I prefer to combine scripts as much as possible. Whether performance is impacted greatly depends on your use-case. I think that unless your doing really time sensitive things or interacting with the AHK process itself, you're pretty safe.

Don't multiple files means mutliple threads ?

Which means it could be faster if you seperate those to mutliple ones.

[Nextron]

True, multiple threads may improve speed. Like I said, it greatly depend on your use-case. Having multiple scripts for simple text replacement hotkeys may decrease performance: SendInput reverts to SendEvent, multiple hooks are processed (sequentially). On the other hand, CPU heavy (compression) or slow tasks (writing/uploading files) may block execution of other tasks unless those are executed as a separate process.

In your situation it is clear: Hook of script A blocks a key which is required in script B. Either you:
• Execute script B after A.
• Run script B as admin, and A as a regular user.
• Combine those element in a single script.
A fourth option would be to not block the CapsLock key so it remains visible, but set it to off as soon as it turns on, but you'll end up with a LED that flashes on each time.

[dsewq1LYJ]

True, multiple threads may improve speed. Like I said, it greatly depend on your use-case. Having multiple scripts for simple text replacement hotkeys may decrease performance: SendInput reverts to SendEvent, multiple hooks are processed (sequentially). On the other hand, CPU heavy (compression) or slow tasks (writing/uploading files) may block execution of other tasks unless those are executed as a separate process.

In your situation it is clear: Hook of script A blocks a key which is required in script B. Either you:
• Execute script B after A.
• Run script B as admin, and A as a regular user.
• Combine those element in a single script.
A fourth option would be to not block the CapsLock key so it remains visible, but set it to off as soon as it turns on, but you'll end up with a LED that flashes on each time.

Thank you so much for those explnations.