[Fixed] Combinatin always give me wrong send letters.

[dsewq1LYJ]

e.g.

Code: Select all

#SingleInstance force

CapsLock & p::Send,FOOBAR

Q1.
If your CapsLock is off.
once you trigger the Hotkey it gives you "foobar"(lowercase) [btw --- CapsLock is on now]
and AHK knows you are using the CapsLock combination,
it revert the CapsLock back to the off and the second will spawn "FOOBAR"

what's the problem ?
and how to solve it !?

Q2.
Is possible to force one Send command to gives always lowercase letter ?

I need this feature to prevent the Vim will not gives wrong command or I need to toggle the CapsLock always.

Hope someone can understand what I mean,
If you couldn't.Tell me.I'll improve my describing as best I can.

[lexikos]

It seems you can work around it like this:

Code: Select all

CapsLock & p::
KeyWait CapsLock
Send FOOBAR
return

[dsewq1LYJ]

It seems you can work around it like this:

Code: Select all

CapsLock & p::
KeyWait CapsLock
Send FOOBAR
return

But I need to release the CapsLock key to spawn "FOOBAR"?

Is possible make it can trigger by "Press Down" event !?

because I wanna rebind the "CapsLock & p" to navigate (Scroll down) my Application,
and If I wanna Scroll down 6 times...I need to release the CapsLock button 6 times...
It's not efficient : [

[lexikos]

I think there's some conflict between Send saving/restoring CapsLock and the custom combination hotkey trying to preserve CapsLock functionality. (CapsLock and other modifier keys get special treatment for custom combinations, whereas normal keys which are used as custom modifiers are blocked by default.)

I have found that if another script blocks CapsLock (i.e. with a CapsLock:: hotkey), your script produces "FOOBAR" but also toggles CapsLock.

This appears to work:

Code: Select all

CapsLock & p::
SetCapsLockState Off
Send FOOBAR
return

I have moved the topic to Bug Reports so that I don't forget to look into it further.

[dsewq1LYJ]

I think there's some conflict between Send saving/restoring CapsLock and the custom combination hotkey trying to preserve CapsLock functionality. (CapsLocek and other modifier keys get special treatment for custom combinations, whereas normal keys which are used as custom modifiers are blocked by default.)

I have found that if another script blocks CapsLock (i.e. with a CapsLock:: hotkey), your script produces "FOOBAR" but also toggles CapsLock.

This appears to work:

Code: Select all

CapsLock & p::
SetCapsLockState Off
Send FOOBAR
return

I have moved the topic to Bug Reports so that I don't forget to look into it further.

Thanks a lot !
and please one more question Lexikos Sir ~
Is any colorscheme of AHK(lastest ver.) for Vim !?
My vim does not support such follow new command(didn't highlighted).

SetRegView
Font
Color
Margin
...etc

so...I keep using AHKSciTE and maybe its still the best Editor of AHK ?

Edit:
I did realized my post move to Bug report.
Sorry about the wrong place to post, and yeah AHK is still great !

[guest3456]

Is any colorscheme of AHK(lastest ver.) for Vim !?
My vim does not support such follow new command(didn't highlighted).

SetRegView
Font
Color
Margin
...etc

you can easily edit the vim colorscheme file to include those keywords

if you are using the built-in syntax file that ships with Vim, then look in the syntax folder for the "autohotkey.vim" file

[dsewq1LYJ]

Is any colorscheme of AHK(lastest ver.) for Vim !?
My vim does not support such follow new command(didn't highlighted).

SetRegView
Font
Color
Margin
...etc

you can easily edit the vim colorscheme file to include those keywords

if you are using the built-in syntax file that ships with Vim, then look in the syntax folder for the "autohotkey.vim" file

Thanks : ]

I am new in vim, and I am totally stuck in it...it's script is pretty useful so...
I'll give it a try !

[lexikos]

I did realized my post move to Bug report.
Sorry about the wrong place to post, and yeah AHK is still great !

FYI, you posted in the right place.

[lexikos]

Please confirm that v1.1.22.05 fixes your issue.

[dsewq1LYJ]

Please confirm that v1.1.22.05 fixes your issue.

Deeply thanks !

It works like a charm

Awesome !