Difference between revisions of "AMOS:Bug Commands after data statements"
Lonewolf10 (talk | contribs) (Added "Commands After Data Statements Crash AMOS" details) |
Lonewolf10 (talk | contribs) m (→Commands After Data Statements Crash AMOS: minor page edit.) |
||
| Line 2: | Line 2: | ||
This will crash AMOS: | This will crash AMOS: | ||
| − | + | Data 10,10,20,34,56,98,34,21 : Rem data for image play | |
| − | Data 10,10,20,34,56,98,34,21 : Rem data for image play | ||
This is perfectly fine: | This is perfectly fine: | ||
| − | + | Rem data for image play | |
| − | Rem data for image play | + | Data 10,10,20,34,56,98,34,21 |
| − | Data 10,10,20,34,56,98,34,21 | ||
NB: Data statements must also be listed before any procedures in your program otherwise the Editor will think they don't exist! For this reason it is best to use Data statements as a temporary measure when programming and put the data into an AMOS Bank once all the data is complete. | NB: Data statements must also be listed before any procedures in your program otherwise the Editor will think they don't exist! For this reason it is best to use Data statements as a temporary measure when programming and put the data into an AMOS Bank once all the data is complete. | ||
Latest revision as of 00:44, 10 December 2007
Commands After Data Statements Crash AMOS
This will crash AMOS:
Data 10,10,20,34,56,98,34,21 : Rem data for image play
This is perfectly fine:
Rem data for image play
Data 10,10,20,34,56,98,34,21
NB: Data statements must also be listed before any procedures in your program otherwise the Editor will think they don't exist! For this reason it is best to use Data statements as a temporary measure when programming and put the data into an AMOS Bank once all the data is complete.
