Thread high priority does not work?

[afe]

Hello,
When the priority of a subroutine is set to 1, even if the priority of the GuiSize subroutine is set to a higher level, it will not be executed immediately. Why?

As in the example below, when the TEST button is pressed, the window is zoomed within 5 seconds and the edit control is not redrawn.

Code: Select all

Gui, +Resize
Gui, Add, Edit, w380 vedit
Gui, Add, Button,, TEST
Gui, Show, h200 w400
return

GuiSize:
Thread, Priority, 2
GuiControl, MoveDraw, edit, % "w" A_GuiWidth - 20
return

ButtonTEST:
Thread, Priority, 1
sleep, 5000
return

[lexikos]

The GuiSize subroutine is not a thread. A thread starts, the subroutine is called, then your subroutine calls Thread, Priority, which sets the priority of the current thread. If you haven't called Thread yet, it is not relevant. If the thread cannot start because the GUI event's priority is too low, Thread will not be called.

All GUI events have a priority of 0.

[afe]

So can the GuiSize subroutine be executed first?

My script is similar to the example above. Since I don't want to interrupt a function thread, I set its priority to 1, but this causes the implementation of the function, as shown in the above example, when the window is zoomed, GuiSize will not be executed immediately.

[afe]

However, in the following example, when the TEST button is pressed first, and then the TEST2 button is pressed, the TEST2 thread is not executed immediately. Why?

Code: Select all

Gui, Add, Button,, TEST
Gui, Add, Button,, TEST2
Gui, Show, h200 w400
return

ButtonTEST:
Thread, Priority, 1
sleep, 5000
return

ButtonTEST2:
Thread, Priority, 2
msgbox OK
return

[jNizM]

While sleeping, new threads can be launched via hotkey, custom menu item, or timer.
(https://www.autohotkey.com/docs/commands/Sleep.htm#Remarks)

If you can, try to avoid using sleep as much as possible.

[afe]

I removed Sleep, but the results were the same. TEST2 does not interrupt the TEST thread.

Code: Select all

Gui, Add, Button,, TEST
Gui, Add, Button,, TEST2
Gui, Add, ListView,, TEST
Gui, Show, h200 w400
return

ButtonTEST:
Thread, Priority, 1
i := 0
Loop, 10000
LV_Add(,++i)
return

ButtonTEST2:
Thread, Priority, 2
msgbox OK
return

[swagfag]

did u not see what @lexikos wrote? gui event handlers have default priority of 0.

at most u could lower(read: assign negative) the priority of (all) threads accordingly to ensure gui handlers are still at least able to interrupt them