AutoHotkey Community

Others built-in functions derivated from commands would be welcome, for example :
if KeyWait(KeyName [, Options]) = F8 ; etc...
... and probably most for the ones witch have an OutputVar parameter like :
if GuiControlGet([Sub-command, ControlID, Param4]) = xxx
if ControlGet(Cmd [, Value, Control, WinTitle, WinText, ExcludeTitle, ExcludeText]) = xxx
if WinGetText([WinTitle, WinText, ExcludeTitle, ExcludeText] = xxx
if Transform(Cmd, Value1 [, Value2]) = xxx
and so on for Input, IniRead, etc
There is aprox 40 commands with an OutputVar parameter.

Is it a good idea ? It isn't too much work for not so much usage ?

I don't know but I think it should be a good thing...

Edit : Sorry I didn't seen before posting the Titan's "Commands Function Collection" topic in the "Scripts & Functions" forum...
But may be these functions in an internal form like the "Frequently-used Functions" ???
May be I was looking to the finger ?

There are plans to build in more of these (to the extent that they don't add any measurable code size). However, adding more GUI features (such as more control types) is a higher priority at the moment.

Thanks for giving details about how some of them may work, and for determining that there are about 40 remaining.

Thanks for your reply. I clarify : there are about 40 commands with an OutputVar parameter in totality (found with the search facility of the help file). May be, like KeyWait, other commands without an integrated return parameter ca be usefully converted in functions. Of course it isn't a higher priority, but may be it can be done easyly, as the code for the command already exist (may be I'm wrong)
Thanks for the superb work. I'm an AutoHotKey fan...