My aim is to support a kind of batch files for CE devices (Filecopy, loop, expressions), window automation (Send, Winactivate) and most common gui commands.
Some functions are not working, because there's no API-call for some functions on WindowsCE.
Some functions are requiring system-dlls, which are not present on i.e. a PNA so I had to comment them out.
Some functions are different between Win and WinCE so they have to be reimplemented. Such less important functions (i.e. sound) will not be implement, but the code can be changed by everybody else of course.
NEW: If AHKCE is working on your device, please pm me and tell me the name of your device. I'll create a list of working devices.
If you are starting the EXE it looks for a file AutohotkeyCE.ahk which is started automatically.
The best thing to start is using the following script from sergeich. Please copy his code to a file named "autohotkeyCE.ahk" and run the exe.
Now the extension ahk is "bundled" with the autohotkeyce.exe. You can now start your favorite script directly.
RegWrite, REG_SZ, HKEY_CLASSES_ROOT, .ahk, , AutoHotkeyScript RegWrite, REG_SZ, HKEY_CLASSES_ROOT, AutoHotkeyScript, , AutoHotkey Script RegWrite, REG_SZ, HKEY_CLASSES_ROOT, AutoHotkeyScript\Shell\Open\Command, , "%A_AhkPath%" "`%1" RegWrite, REG_SZ, HKEY_CLASSES_ROOT, AutoHotkeyScript\DefaultIcon, , %A_AhkPath%`,`-160Place the AutohotkeyCE.ahk file in the same folder as the EXE and ahkCE is starting the script
The main problem is the memory (or stack) space. A lot of functions are not working because the stack is corrupt after a function call. These functions have to be rewritten or the allocation must be done with new/delete.
The first attempt of a compiler. Please read that post:
You can find a list of working / not working commands here
The changelog is here