AutoHotkey Community

From this thread: http://www.autohotkey.com/forum/viewtopic.php?t=49044

I think this is an bug. Not sure if this is documented, but this should be changed. It is unlogical and not strict that a comma after the word "Yes" is required:


works, but ...

does not work.

Technically it's not a bug because it's documented that, "The One True Brace (OTB) style may optionally be used with if-statements that are expressions (but not traditional if-statements)." Also, it's documented somewhere that only the first comma of a command is optional.

Although it probably wouldn't be that complicated to support OTB for IfMsgBox, neither would it be trivial. Another drawback is that it would make IfMsgBox inconsistent with the lack of OTB support in other commands like IfExist, IfInString, and IfWinExist.

So I'm inclined not to change this. Other opinions are welcome.

My inclination is to ask for IfMsgBox to become deprecated. It's one of the few 'Old style' ifs that does not have a direct replacement (that I know of) with an expression-if.

Ideally, I'd like to see a msgbox's result in A_MsgBox or something like that, which would allow for OTB as well as deprecating IfMsgBox.


On a side note, I'd like to see a note in the docs that certain commands are deprecated and a link to http://en.wikipedia.org/wiki/Deprecation or similar, and a suggestion to use the newer syntax.

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ

well perhaps something like this is more appropriate turn msg box to a function





however i do like yours as well

_________________
No matter what your oppinion Please join this discussion
Formal request to Polyethene

Thanks for the A_MsgBox idea. I don't know how high a priority it should be, but it should be kept in mind for the future.

Hey, I like the idea of having A_MsgBox very much. That would be really ideal, in the sense of current Ahk (Command type). This was originally a (to me bug) report of something that did not work and now we have a new suggestion. cool

I don't mind features being officially and indefinitely deprecated, as long as they're not actually eliminated. As powerful and useful as expression syntax has become in various aspects of AutoHotkey, the old-school "IfCondition" commands still retain their usefulness in terms of clarity and compactness, along with other non-expression commands such as SetEnv. Call me a dinosaur, but I occasionally use one-liners like... and I also like Coke Classic!

I am however all for also having an A_MsgBox variable to refer to, as long as the rules for its persistence and for the manner in which it might be affected by a MsgBox in another thread are made clear.

Jacques.

that is the definition of deprecated. It makes sure olde scripts don't break, but it is discouraged for new scripts.

Other threads shouldn't affect A_MsgBox much (A_MsgBoxResult?), since there are other built-in variables that keep the results per thread. Some interesting constructs could be made if the value were allowed to 'hop' threads, though. Those same constructs can also be easily managed with a global var too.

IMHO one-liners like that are harder to read than the 3-line equivalent. That's a personal syntax style opinion, though, and not an invitation for a flamewar

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ

No worries, not my style. Plus I'm a big believer in personal choice and recognize that different programmers have different perceptions of what constitutes readable syntax. I just happen to favor compactness (see the APL discussion at http://www.autohotkey.com/forum/viewtopic.php?t=13995&start=24).

Jacques.