nrmh

@Synapsee, you linked to the same pages I linked to, quoting things from the same pages. You've shown two methods that appear to do the same thing as my snippet, but I don't know if they're actually the same; hence my question. Is it more idiomatically correct to refer to the documentation and use the listed default values? And is using the Default keyword even consistently correct? This is, are there any built-in functions in which Default will not do the same thing as writing the default listed values in the documentation? I understand that for UDFs, Default may not work, depending on the implementation; however, to my knowledge, the built-in functions aren't implemented in AU3; thus it would presumably be the job of the lexer to implement Default on a global level, which makes me think that Default should behave universally across all built-in functions.

I'm asking the same thing as this question, but it didn't get a clear answer, so I figured I'd ask more directly. It appears that I can use the Default keyword in place of specifying a value to an optional parameter to have it behave as if I didn't specify anything all, while allowing me to specify optional parameters afterwards, like so: GuiCreate("Title", 100, 100, Default, Default, $Style) Is this the correct idiomatic method of skipping optional parameters to specify later ones? Additionally, is there any gotchas I may have to look out for while doing this?