AutoHotkey Community

Thanks to Lexikos, the release has been fixed so that bitwise operations involving floating point variables don't wrongly cache those variables as integers. Without the correction, the following example shows "2" instead of the expected "3.000000":
The topmost post has been updated with the following links:
www.autohotkey.com/misc/AutoHotkey-Pre-1.0.48-new3.exe (238 KB)
www.autohotkey.com/misc/AutoHotkey-Pre- ... N-new2.zip (240 KB) (BIN file for making compiled scripts)

The link still points to the old AutoHotkeySC.bin, w/o the bugfix, so compiled scripts still show 2 intead of 3.000000 with the test script. In the first post there are two links to the bin file, which needed update.

Thanks. I've fixed the BIN/compiler ZIP file to contain the new version instead of the old one. All the old links (in case anyone has saved them or they appear elsewhere in the topic) also contain the newest versions.

Hi Chris,

really great the idea of storing the real number as binary (Real*8 = Double = precision 15 decimal digits) and not as a string and thanks for your work.

I was waiting for that: Date + time calculation starting in 1582 needs 14 digits for msec precision. Used "SetFormat Float 0.16E" before.



May be it could be better to have a conversion routine instead of a format statement that only works on direct output (e.g. Msgbox) like

which could be used in composing out-string too.

That is good, though it would take a while to research and design something that's flexible yet intuitive. By contrast, extending SetFormat is almost trivial and would require minimal changes to any existing scripts that need maximize performance.

I expect your idea will be implemented in some future version, especially a major version like v2 that is expected to have more functions and fewer commands. Perhaps more things like FormatTime could be added after researching other languages for the best syntax. It would also be good to have some date/time functions to provide a more intuitive way to compare and manipulate dates and times.

Thanks.

Here they are:
http://sourceforge.net/projects/datetimelib/

In short:

Library routines for computation of date and time functions since the Gregorian Calendar was introduced on 1582-Oct-15:

- add/subtract days&hh:mm:ss to/from a given date&time
- with variables type Double: exact calculations down to 0.001 sec (1 msec)
- considered all leap years (the anormalities every 4, 100 and 400 years)
- considered the changes from summer time (Daylight Saving Time DST) to winter time and back
- compute the start and end dates of DST for a given year
- compute UTC (Universal Time = Greenwich Time) to local time; considered DST
- compute weekdays
- convert to Excel compatible date/time values
- template for your own implementation
- documentation inside the routines and in a handbook

To avoid code bloat, AutoHotkey currently uses the Windows API for date/time math. Hopefully it is just as accurate as the library above.

It is AHK lib..

_________________
URLGet - Internet Explorer based Downloader
StartEx - Portable Shortcut Link

I have a small hotkey to start a new empty notepad.

;New Notepad
^!n::Run notepad.exe

But since the new beta version, I always starts in the background and I have to click on the taskbar icon.
With the previous version, I was the topmost program

No changes were made to those parts of the program. So it could just be a timing issue or some OS quirk.

What am I doing wrong? I can't get scripts to compile successfully using the NoDecompile switch. Are you sure the version in the zip file is the right one? (After all, the zip file says "new2" not "new3"...)

I've successfully tested the NoDecompile switch with this version. So perhaps your version of Ahk2Exe is too old. Try replacing it with the following: www.autohotkey.com/misc/Ahk2Exe-1.0.47.06.zip

Thank-you, that fixed it.

Have been checking the beta on some scripts and am indeed seeing faster performance.

One strange behaviour on same script between its uncompiled and compiled forms. I'm fairly sure I'm using the beta AHK .exe and the beta AHK SC.bin in the Compiler directory.

It's the effect of "SetFormat, integer". Here's a code snippet



If I run this by double clicking the .ahk the second MsgBox reports int1 as "0x64" as expected.

If I compile the script then run the .exe the 2nd MsgBox reports int1 as "100"

I can get the compiled version to report "0x64" by removing the second SetFormat statement.

Would appreciate if anyone could just check this. Should I be doing anything other than installing the AHK beta .exe in the AHK directory and the beta ..SC.bin in the Compiler subdirectory?

This is significant as I use this method to prepare a hex string for writing to a COM port.

Many thanks

Ian

AutoHotkey_L (my custom build) has been updated with bug-fixes and optimizations from the current beta, a fix for the bug reported by Ian, and one new feature.

Chris, the section of code which disables binary number write-caching was omitted from SC builds, along with load-time validation of SetFormat's parameters.