AutoHotkey Community

Hey jackie,

I built a little GUI that allows me to launch a test script based on the various flavors of AHK exes that are out there now:



I just recently tried running a code sample from the AutoHotkey_L documentation through my test script via the GUI:



Using AutoHotkey_L.exe the code runs fine, but when I try to use the latest version of AutoHotkeyU.exe I get this error:



I couldn't see anything obvious in my own scripting but I could be wrong. In your build are the components of AHK_L supposed to be fully integrated and/or supported at this point?

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

Are you sure that was an error of AutoHotkeyU? The above codes works fine here.

How weird, I just tested it on my other computer and it works fine as well. I'll check for other problems on my other computer, sorry to interrupt your thread for a non-issue!

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

sinkfaze: Make sure you're using the latest version of AutoHotkeyU. Older versions didn't have object support.

_________________
fincs
Highly recommended: AutoHotkey_L (see why) (all my code snippets require it)
Formal request to polyethene - I support the unity of the AutoHotkey community
Get SciTE4AutoHotkey v3.0.00 (Release Candidate)
[My project list]

Yeah, I had just downloaded the zip for the latest version to my other computer but I hadn't noticed that it didn't unzip the files to the right directory so it never overwrote the previous version.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

Hello,
Thanks for this Unicode version.
Let me fill a bug report:

This won't work:
<^>!+é::Send É
<^>!+ç::Send Ç
It would rather show ╔ and Ã

So, I need to write this instead:
<^>!+é::Send {ASC 0201}
<^>!+ç::Send {ASC 0199}

This happens no matter how the command file is encoded (UTF-8 or 16LE), no matter if you use Send or SendInput.

However, other characters are shown correctly (œŒăĂ etc.): "Send œ" etc.

Edit: I use this script since I have é and ç on my keyboard, but not É and Ç. "Send É", etc. works with the official AutoHotKey.

Ç(U+00C7) and É(U+00C9) are both in the range between U+0080 and U+00FF. Both of them are valid virtual key codes, so in programming level there might be no way to know either the "character" or the "key code" should be sent. I know it should be a problem for the European users, but I'm not able to fix it currently because I don't have the knowledge about those languages and keymaps.

Send accepts a string of text; possibly with modifiers and {key names} interspersed, but never a raw array of virtual keycodes. Afaik, only 0-9 and A-Z have virtual keycodes matching their ASCII values, so you should not be interpreting anything else directly as a virtual keycode. (Actually, I think AutoHotkey does not directly interpret even those characters.)

VkKeyScanEx is used (via CharToVKAndModifiers <- TextToVK <- SendKeys in keyboard_mouse.cpp) to translate each character into a virtual keycode/modifier combination. If that fails, SendASC is used (via SendKeySpecial) to send the character. Perhaps it would be better to call SendUnicodeChar from SendKeySpecial than having two virtually identical sections for it in SendKeys. In your commit 3804d380.., they are at line 618 and line 710 of keyboard_mouse.cpp.

@Lexikos

Hmm, I'll make SendKeySpecial use SendUnicodeChar, hope it won't break anything.

SendKeySpecial is only used for individual characters which have no corresponding vk+modifiers. It uses Alt+Numpad, which seems to generate a WM_CHAR message (in Notepad/Edit control at least). I presume the majority of applications use WM_CHAR, not the individual Alt+Numpad key-presses. SendInput in Unicode mode also generates a WM_CHAR message, so it will probably work just as well but without the extra key-presses. If it is used on an ANSI window, the character is translated automatically.

Anyway, I meant to suggest that SendKeySpecial be used only in the same situations as before, except that TextToVK is given an opportunity to translate the character first (in both sections). Thinking more about it, this wouldn't have solved the problem as those characters are not > 255. If you have any concern about backward-compatibility, I suggest you change SendKeySpecial as follows:

• Use SendUnicodeChar for characters > 255.
• Use SendASC for characters 0..255.
• Change the following line to work correctly when aChar is a wide char.
  
  Code:
  if (aChar < 0)    // Try using ANSI.
     *cp++ = '0';  // ANSI mode is achieved via leading zero in the Alt+Numpad keystrokes.
  It was meant to detect whether aChar is outside the range 0..127, but only works if aChar is a signed 8-bit integer (char).

Btw...
Visual C++ 2008 does not support Windows NT either. See Visual C++ Breaking Changes. Since your solution file says "Visual Studio 2008", I presume you also compile with 2008. I guess this means that AutoHotkeyU and _L will run only on platforms where SendInput is present and supports the Unicode flag.

So is it needed to send the characters < 255 by SendASC instead of SendUnicodeChar?


I think the source codes might be able to be compiled by VS2005 or VS2003?

I don't think so, unless you're allowing for Win9x/NT.
That's possible, but how many users have VS2005 or VS2003? I was thinking about the more generally available binaries. Is there some other reason it couldn't be run on/compiled for Win9x? (I'm curious, but don't really care to be honest.)

Thanks for the quick answer and glad to see there might be progress with that.

But as I mentioned, Send works with other characters within the same range you mentioned. For instance:
<^>!o::Send œ
<^>!+o::Send Œ

They are still U+009C and U+008C!

FileRead doesn't seem to work with FileEncoding UTF-16-RAW. Windows XP/Server 2003's Backup utility creates "backup selection files" (.bks) in this format. Fortunately, they can be read using FileRead *c filename or with Loop, Read.

Edit: FileRead *c sets the variable's "length" to twice what it should be.
        script2.cpp @ line 9070

Um...

_________________
fincs
Highly recommended: AutoHotkey_L (see why) (all my code snippets require it)
Formal request to polyethene - I support the unity of the AutoHotkey community
Get SciTE4AutoHotkey v3.0.00 (Release Candidate)
[My project list]