GUISetOnEvent or GUIGetMsg

[Hest]

Normally I use GUIGetMsg in my scripts, but I have just played around with GUISetOnEven. Both are working fine, but is one better than the other and why?

Whats the best one to use or does it depend on what I'm making or is there any performance difference?

I made an excample where I read something from Commandline and the script with GUISetOnEvent could be closed at once, where the other one would need a little extra time, I guess thats one of the differences?

Can someone please explain to me whats best and why.

Thanks in advance

Edited June 22, 2009 by Hest

[PsaltyDS]

Normally I use GUIGetMsg in my scripts, but I have just played around with GUISetOnEven. Both are working fine, but is one better than the other and why?

Whats the best one to use or does it depend on whay I'm making?

I made an excample where I read something from Commandline and the script with GUISetOnEvent could be closed at once, where the other one would need a little extra time, I guess thats one of the differences?

Can someone please explain to me whats best and why.

Thanks in advance

It's a trade off between simplicity (GuiGetMsg), and capability (GuiOnEventMode).

If your script doesn't have much work to do while waiting for GUI inputs, and you don't need to handle additional GUI inputs while the earlier is handled, then the message loop is quick and easy to code.

However, if your script is very busy, and you want to get other things done during the time you are not handling new GUI inputs, and if you need one GUI action to interrupt the processing of another, then you need event mode.