Author |
Topic: Disappearing BASIC (Read 1455 times) |
|
KenDown
Full Member
member is offline
Posts: 181
|
 |
Re: Disappearing BASIC
« Reply #2 on: Mar 9th, 2014, 8:24pm » |
|
Thanks, though that is a counsel of perfection, particularly when writing a program. You write d*2 instead of d%*2 and the program comes to a crashing halt (and even worse if the mistake is in PROCerror which should be closing all the bits and pieces you mention!
Nevertheless, I bodge along quite happily with the program crashing and being fixed and restarting and so on - right up until I include an edit window (code copied from your example program) and then the problems start.
So I close down BB4W, I even restart the computer, load the program into BB4W and don't even run it, just scroll through it to find the point where I left off and - bang! Gone!
However, interestingly, I have noticed that once the program is compiled, although the BB4W program still crashes and disappears, the compiled .exe is pretty stable, edit window and all.
Odd.
|
|
 Logged
|
|
|
|
Matt
Developer
member is offline
Gender: 
Posts: 210
|
|
Re: Disappearing BASIC
« Reply #3 on: Mar 9th, 2014, 9:01pm » |
|
on Mar 9th, 2014, 1:59pm, Richard Russell wrote:| Never abort your program by clicking on the 'stop' button in the IDE's toolbar (or the equivalent menu item). |
|
Can I ask - out of curiosity, not criticism - what the need for the STOP button is, then?
Matt
|
|
Logged
|
|
|
|
admin
Administrator
member is offline
Posts: 1145
|
|
Re: Disappearing BASIC
« Reply #4 on: Mar 9th, 2014, 10:46pm » |
|
on Mar 9th, 2014, 9:01pm, Matt wrote:| Can I ask - out of curiosity, not criticism - what the need for the STOP button is, then? |
|
The BB4W documentation tells you. Here's a link to the relevant section of the online manual:
http://www.bbcbasic.co.uk/bbcwin/manual/bbcwin1.html#stop
As it says, the STOP button is for use as a last resort when nothing else works.
Richard.
|
|
Logged
|
|
|
|
admin
Administrator
member is offline
Posts: 1145
|
|
Re: Disappearing BASIC
« Reply #5 on: Mar 9th, 2014, 10:48pm » |
|
on Mar 9th, 2014, 8:24pm, KenDown wrote:| Thanks, though that is a counsel of perfection, particularly when writing a program. You write d*2 instead of d%*2 and the program comes to a crashing halt |
|
Please don't use the emotive word 'crash' out of context. Writing d*2 rather than d%*2 does not result in a crash, it results in an error being reported (probably 'No such variable'). BB4W is not prone to crashing!
Quote:| Nevertheless, I bodge along quite happily with the program crashing |
|
If you follow the recommendations I gave, it will not crash. They are things that every program should do anyway, but they become more important in the rare case when the program creates a new thread.
Quote:| until I include an edit window (code copied from your example program) and then the problems start. |
|
If the example you are referring to is TEXTEDIT.BBC, that does not create a new thread, and cannot crash BB4W in the way you describe (at least, not with the current version of WINLIB5; there may have been a very old version of that library that did create a new thread).
If in doubt, run TEXTEDIT.BBC itself; it will not cause the IDE to crash, even if you use the Stop button.
Richard.
|
| « Last Edit: Mar 9th, 2014, 10:51pm by admin » |
Logged
|
|
|
|
|
