Jump to content

Sky Slate Blueberry Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate

Sending strings fails in some cases


  • Please log in to reply
4 replies to this topic
  • Guests
  • Last active:
  • Joined: --
Hi,

I have noticed that sending a sting fails if the character is present in the character tables of the keyboard layout, but is produced with a rare modifier which is not crtl, alt or shift.

I am using the Neo2 layout (<!-- m -->http://en.wikipedia....oard_layout#Neo<!-- m -->). This layout uses some extra layers which are accessed with kana (a far east modifier) and a complete new modifier.

::test1::¹²³ will give you “123” because ¹²³ are on one of the new layers above 123 (accessed with the new modifier).
::test2:: ₁₂₃ will give you “°§ℓ” (which is 123 with shift) because this layer is accessed with shift and the new modifier.

I have no problems to send characters which are not in the character table:

::test3::⁈⁉ will give you actually “⁉⁈”

IMHO AutoHotkey should not only check if the character is listed in keyboard layouts character table, but also if it’s able to handle its modifier. If not it should send the character like those not present in the layout table

I know the Neo2 layout is a complete new layout, but I am pretty sure it affects many far east layouts (that use kana), too.

I am using the latest AutoHotkey_L (unicode and 32bit)

tonne
  • Members
  • 1654 posts
  • Last active: May 06 2014 06:22 PM
  • Joined: 06 Jun 2006
Did you save in UTF-8?

  • Guests
  • Last active:
  • Joined: --
yes, the script is saved as UTF-8.

I stumbled across this problem some time ago and now I’ve read in these threads¹² about the same problem.

¹ http://de.autohotkey...opic.php?t=8654 (german)
² http://www.autohotke...topic72249.html (english)

  • Guests
  • Last active:
  • Joined: --
http://www.autohotke...351.html#447351
This thread presents a workaround by introducing {Uni}, a send mode which avoids sending keystrokes.

Maybe a developer of AutoHotkey can add it for future builds of AutoHotkey_L

Lexikos
  • Administrators
  • 9844 posts
  • AutoHotkey Foundation
  • Last active:
  • Joined: 17 Oct 2006
I'm not sure if it will (completely) solve your problem, but I have made a change in v1.1.00.01 which may help.

Added check to avoid incorrectly sending keystrokes for characters which actually require the "hankoku" key.

The "hankaku" key is the only modifier supported by VkKeyScanEx and not AutoHotkey. (I just realised that I, unfortunately, mispelled the name.)

Update on 2011-08-06: I believe this change only covered Mod3, not Mod4. See this post for more details.