tic wrote:
Do you really need a 64 bit version then? Surely the 32 bit one would be fine if its just for the installer
I'm not sure that would work either:
In general, 32- and 64-bit Microsoft Installer (MSI) packages are treated in the same way except for how Windows Installer treats folder variables such as [Program Files] and [System Folder], and how it writes components into the registry or GAC. When you create a 32- or 64-bit MSI package, the processor architecture is noted in the .NET Framework assembly's strong name identity when it is installed in the GAC.
While you can dynamically set the default install path (ProgramFiles or ProgramFiles64) and registry keys, the
platform attribute has to be static. It makes no sense having a 64bit installation with 32bit DLLs in the GAC. I will look into this further for the next release, there might be a way to overcome this problem.
tic wrote:
I would like to help with gdi+ but have the concern that the same methods couldnt be used as it is all very dll reliant. For example, I have no knowledge of how to create the equivalent of a layered window under mac/linux
System.Drawing is a managed wrapper and will be used for built-in GDI+ commands in a future version. DllCalls to gdi32.dll will only ever work on Windows.
W00tW00t wrote:
I think IRONAHK will be worthless, unless it can execute any and all present ahk code, including Windows DLL calls
I agree. Apart from
pointers, DllCall already works.
W00tW00t wrote:
Translation is hard, but it would be a worthy thing if someone is smart enough to pull this off.....
It's rather straightforward as it only involves a good understanding of AutoHotkey from the source (not just the documentation) and the ability to write a cross platform version in C#. This is what I have been doing in my spare time since October 09 and if version 0.5.5 is any indication of progress you could guess how much work is outstanding.
OceanMachine wrote:
I am looking at the documentation (e.g.
http://www.ironahk.net/docs/commands/msgbox) and I am getting a 404 for every page.
Looks like the cron script for updating the site didn't run as expected but it should be working now, thanks.