AutoHotkey Community

[icefire]

My apologies if this turns out not to be a bug but here goes.

I have been using “SetFormat, float” in a script and have found some strange behaviour. I am not sure if it is a bug or something I have missed. But I cannot find anything in the help file to explain it.

The problem is when using SetFormat within a subroutine. The first time the subroutine is performed, through dropping into it (rather than from a tray menu execution), it alters the float format as expected and the alteration also correctly takes effect in a subroutine which did not itself contain a SetFormat statement.

However, when the ChooseDigits subroutine that contains SetFormat is called from the tray menu, it only works within that subroutine and, surprisingly, not within the other subroutine.

Although my original script was fairly involved, I have appended, below, a (persistent) script stripped to the bare minimum to demonstrate the problem.

If you run the script, proceed as follows.
Input an integer to be used within the SetFormat command. Say you choose 3.
A message box will display the value of the system variable A_FormatFloat.
In this example, it will be 03.
Then choose TestMessage from the tray menu.
That will show the value of A_FormatFloat as it appears in the TestMessage subroutine.
In this example, it will be 03.
So far, so good.

Now select ChooseDigits from the tray menu.
Input a different value.
Say you choose 5.
A message box will display the value of the system variable A_FormatFloat.
In this example, it will be 05.
Then choose TestMessage from the tray menu again.
That will show the value of A_FormatFloat as it appears in the TestMessage subroutine.
In this example, I would expect it to be 05.
But in fact, it will be 03, the value set the first time around.

Is that a bug? I cannot understand why A_FormatFloat was set as expected in the TestMessage subroutine the first time (when execution dropped into the ChooseDigits subroutine) but not the second time (when ChooseDigits was called from the tray menu).

If you insert the following line of code as the first line of the TestMessage subroutine:
SetFormat, float, %MyFloatFormat%
the script then behaves as I would expect it to do even though I would not expect that additional line to be necessary.

If you insert the following above the ChooseDigits label
MsgBox, Select ChooseDigits from the tray menu
Exit

it proves that the ChooseDigits subroutine does not alter A-FormatFloat in the TestMessage subroutine at all when ChooseDigits is called from the tray menu. Thus, it only works globally if it is dropped into rather than called from the tray menu.

I am using version 1.0.13 on Windows 98SE.

Here is the script:

#Persistent
Gosub, SetMenu


ChooseDigits:
InputBox, MyDigit, Number of Digits, Enter number of digits for float format: integer between 1 and 9, , 400, 189
AutoTrim, Off
MyFloatFormat = 0%MyDigit%
SetFormat, float, %MyFloatFormat%
MsgBox, ChooseDigits Subroutine`n`nA_FormatFloat = %A_FormatFloat%
MsgBox, Now select "TestMessage" from the tray menu
Return


TestMessage:
MsgBox, TestMessage Subroutine`n`nA_FormatFloat = %A_FormatFloat%`n`n%MyFloatFormat% expected
MsgBox, Now select "ChooseDigits" from the tray menu and input a different number
Return



SetMenu:
Menu, Tray, Add, ChooseDigits
Menu, Tray, Add, TestMessage
Return

[Chris]

From my test of your script, I believe this behavior is both normal and documented. Here are the rules that apply in this case:

1) The auto-execute section does not end until the first return, exit, or hotkey label is encountered.

2) The default for SetFormat (and many other settings) is put into effect after 100ms if the auto-execute section takes longer than that to execute (which this one does since it falls right into the ChooseDigits subroutine).

3) In this case, because your auto-execute section takes a long time to finish due to the dialog, the chosen default is put into effect when the first return is encountered.

4) Newly launched threads from a hotkey or custom menu item always start out fresh with the defaults as set in the auto-execute section (in this case, the standard default of 0.6 is the global default until the user choses a new one in the InputBox).

It is usually best to have the auto-execute section set the required defaults right at the very top. Then, those defaults will always be in effect for every newly launched thread, whether it be launched by hotkey, menu, or SetTimer.

The other big thing to keep in mind is that changes made to settings such as SetFormat and KeyDelay by one thread will not affect the others. This is done so that you don't have to continually worry about "putting back" the right default value prior to returning from a hotkey or menu subroutine that may have temporarily altered it for its own purposes.

This is discussed in the Scripts section at http://www.autohotkey.com/docs/Scripts.htm -- which I've updated to mention menus and SetFormat. If you find any other omissions or anything that needs clarification, let me know.

Thanks,
Chris

[icefire]

Thank you for the reply. Now I understand it! That is a beautifully clear explanation and somewhat explicitly clearer than the original http://www.autohotkey.com/docs/Scripts.htm section.

I think the very important point that I had not quite grasped is:

[Chris]

Thanks for the suggestion. I've added the following to the Scripts page: "Also note that each thread retains its own collection of the above settings. Changes made to those settings will not affect other threads."