#63 'run' --> 'jump' is a dreadful title

[Christian Blackburn]

Problem:
In the context of debuging the word jump implies moving
from one place to another probably out of sequence.
However in the run menu jump seams to mean the status
of whether or not the application is running.

Repro:
(On Windows 2000 Pro Sp3)
1. Start XBasic 6.2.3
2. Click "file" --> "load"
3. Double-Click "demo" in the "dir" list box
4. Double-Click "tlist.x" in the "file" list box
5. Click "run" --> "jump"
6. Click [Cancel]
7. Click "run" --> "start"
8. In XBasic Click "run" --> "jump"

Result:
Every time jump is executed it seems to show the
"running/not running status" of the application and
never "jumps" to a particular line of code.

After Step #5:
The Following Window appears:
"message
RunJump()
program not running
[cancel]".

After Step#6:
The Following Window appears:
"message
RunJump()
program currently running
[cancel]".

Exptected:
The "run" --> "jump" menu item should be called
"application state".
The message window that appears should also bear the
title of "application state" rather than "message"
which is merely stating the obvious. Of course it's a
message there's text, that's self-explanatory.
Secondly "RunJump()" shouldn't be listed on the form.
XBasic programmers are uninterested in the internal
name of the RunJump function. They simply want to get
the status of the application and go back to coding.
Why not say "Your application is not running at this
time. You can click "run" --> "start" or press F1 to
start your application." Such a message should be
followed by an [OK] button and not a cancel button (if
possible). Cancel just doesn't make contexual sense.
For further support on my OK is better than cancel
opinion please see another bug I wrote:
http://sourceforge.net/tracker/index.php?func=detail&aid=700301&group_id=1657&atid=101657