| Commit | Date | |
|---|---|---|
| 2018-04-01 01:32:40 | Tree | |
| 2018-04-01 01:22:12 | Tree | |
| 2018-03-31 22:50:19 | Tree | |
|
[r4569]
by
david_costanzo
Remove some redundant code in lportreadarray() |
2018-03-25 02:15:25 | Tree |
|
[r4568]
by
david_costanzo
Replace "char rxchar[64]" with "char rxchar", since only one byte was used. |
2018-03-25 02:08:57 | Tree |
|
[r4567]
by
david_costanzo
Reduce the scope of the "#ifndef WX_PURE" blocks so that more of FMSLogo is compiled for GNU/Linux |
2018-03-25 02:04:54 | Tree |
| 2018-03-25 01:53:12 | Tree | |
|
[r4565]
by
david_costanzo
Fix Bug #514; PORTWRITEARRAY now writes ' ' instead of random memory for non-int items in its array input Throwing a bad input error risked compatibility problems. Writing NUL would break old text-based protocols that use COM communication. Writing an ASCII space seemed to be the safest way to ignore garbage input. |
2018-03-25 01:48:14 | Tree |
|
[r4564]
by
david_costanzo
Fix bug #515; PORTWRITEARRAY now throws a "doesn't like input" error for its second input. The motivation for this change is that PORTWRITEARRAY used to show a message which incorrectly referred to the first input when given a non-array second input. I could have instead corrected the text, but that would have left the non-English translations incorrect. This fix makes PORTWRITEARRAY act more like a typical FMSLogo procedure, throwing an error instead of displaying a dialog box that cannot be interacted with programmatically. Since, after showing the dialog box with the incorrect message, PORTWRITEARRAY used to throw a "Stopping..." error, changing this to throwing a "Doesn't like input" error has negligable risk to backward compatibility. |
2018-03-25 00:31:10 | Tree |
|
[r4563]
by
david_costanzo
Update the documentation for PORTWRITECHAR to match the implementation. |
2018-03-19 02:08:27 | Tree |