If NOT @LOGONMODE
	Break ON
EndIf
Dim $SO
$SO = SetOption("Explicit","On")
$SO = SetOption("NoMacrosInStrings","On")
$SO = SetOption("NoVarsInStrings","On")
$SO = SetOption("WrapAtEOL","On")

$SO = MessageBox("Hello World","My First KiX Script")
? "Return Value: " + $SO
? "Error " + @ERROR + ": " + @SERROR
? "Kix Version: " + @KIX

Return Value: 1
Error 1: Onjuiste functie.
Kix Version: 4.53 Release Candidate 1

Get $SO /A
? "Key: " + $SO[0]
? "KeyCode: " + $SO[1]

• I think checking @ERROR or checking the Return Value for totally the same *value* does not require big recoding.
  
• I would also think that most coders would use the return value to check what key is pressed in MessageBox. Just as it is documented.
  

Quote:

---

The problem is that because it has never worked this way changing the @ERROR value will break existing scripts.

Although it has caught you out AFAIK you are the first person, so it is a very rare event. In fact you might be the first person to have ever checked for a (real) error condition following a MessageBox()!

---

Quote:

---

"Will" sounds so certain. I would prefer to say "might" since I doubt may people actually work with the @Error returned by MessageBox()

---

I actually had "could" at first but "could" or "might" implies a very small chance that any script will break. However given the amount of scripts that are out there it is actually very likely that a change is going to break a number. It's also very likely that it will be a very small number.

Dim $SO
Get $SO
? "Key: " + $SO
? "Error " + @ERROR + ": " + @SERROR
? "Result: " + @RESULT
? "KiX: " + @KIX

Key:
Error 59: Er is een onverwachte netwerkfout opgetreden.
Result:
KiX: 4.53 Release Candidate 1

Get $SO /A

• Key, just as now, press "a" and catch "a", Press {TAB} and catch Chr(9)
  
• KeyCode, My A is next to the TAB-key, where most probably your Q is. Press it evt. with Shift, Ctrl or Alt and we should get the same value
  
• Ascii, maybe redundant, Key maybe does the trick, p.e. the enter key would return "13"