[suggest] UniCode hotkeys.

Discuss the future of the AutoHotkey language
_3D_
Posts: 277
Joined: 29 Jan 2014, 14:40

[suggest] UniCode hotkeys.

24 Aug 2017, 06:34

Is it possible hotkeys to become UNICODE?

Creating nonUS hotkeys now possible only if nonUS layout active.
GetKeyVK return value only if right layout is active and 0 in other cases.

Code: Select all

msgBox("ю := " GetKeyVK('ю')) ;cyrillic YU (Bulgarian Layout/Russin Layout)
But in real when user change keyboard layout letter from example return right value.

Code: Select all

ю::msgBox("Error")
Note: The hotkey "ю" will not be active because it does not exist in the current keyboard layout.
Script wait user to confirm, then run but hotkey not exist. It prevent hotkey() to create hotkeys too.

But in some further moment user can change layout and "ю" will exist. It is vice versa if user start in nonUS layout all the same with US hotkeys. So, user can create hotkeys only in script start layout or in active layout.

Code: Select all

y::msgBox("You press Y(es)")
д::msgBox("You press Д(а)") ;You press Yes in bulgarian/russian/serbian and all cyrillic layouts
This script can`t be run.
The same in german/italian/arabic/greek and all nonUS layouts (layouts that have nonUS letters).
AHKv2.0 alpha forever.

Return to “AutoHotkey Development”

Who is online

Users browsing this forum: No registered users and 26 guests