KILL command.
|
01-14-2017, 12:18 PM
Post: #1
|
|||
|
|||
KILL command.
HI,
Why have-I this message (see attachement please), when I am using KILL in a program ? And what it's means ? Gérard. |
|||
01-23-2017, 10:56 AM
Post: #2
|
|||
|
|||
RE: KILL command.
HI,
I had forgotten that was discuss in a old thread from 2015,0929 but I wonder why this error text in french language still remain in FW 10638 ? BTW what about a *STOP* instruction ? Gérard. |
|||
01-23-2017, 01:44 PM
(This post was last modified: 01-23-2017 01:49 PM by DrD.)
Post: #3
|
|||
|
|||
RE: KILL command.
The KILL; command stops a program, (the BREAK; command exits from a loop). What else would you want a STOP command to do?
|
|||
01-23-2017, 02:11 PM
Post: #4
|
|||
|
|||
RE: KILL command.
I would like a command without any string as we see in the attachement. A kind of *GOTO*. And also that the issue in language is corrected. I know it is not very important but...
Thanks for answer. Gérard. |
|||
01-23-2017, 03:21 PM
(This post was last modified: 01-23-2017 03:23 PM by DrD.)
Post: #5
|
|||
|
|||
RE: KILL command.
Quote:A kind of *GOTO*. How does a STOP command work as a GOTO branch? How would stopping a program with STOP be any different than with the KILL command, which stops a program? If you want progress inspection at a STOP point, using the DEBUG; statement at the point of interest, or use DEBUG <filename> provides break point, single step, and variable inspection functionality. You could add numbered trace variables at various points in a program, then stop by testing: IF (trace==xxxx) THEN KILL; END; or similar code. What else would a STOP command need to do? |
|||
01-23-2017, 03:32 PM
(This post was last modified: 01-23-2017 03:34 PM by Han.)
Post: #6
|
|||
|
|||
RE: KILL command.
Regarding the strange symbols:
Normally, the message (in English) should say: "<name of program> Program interrupted" when run from the Programs menu. When run from the command line, one simply gets the error message "Program interrupted." It is quite possible that the system messages for interrupting a program have not been translated properly. EDIT: I just changed my language to Francais and indeed I see the same symbols. It looks like a bug (wrong translation) in the system strings for French. Graph 3D | QPI | SolveSys |
|||
01-23-2017, 03:44 PM
Post: #7
|
|||
|
|||
RE: KILL command.
So this highlights one of the frustrations in dealing with translations...
Basically, this WAS corrected, but later during a subsequent translation the "translation matrix" matched the string to an older "validated translation" and reverted it. I've corrected it yet again and hopefully it will stick this time. TW Although I work for HP, the views and opinions I post here are my own. |
|||
01-23-2017, 03:59 PM
Post: #8
|
|||
|
|||
RE: KILL command.
Thak Team and others. I dont' realy explain what I would like. Impossible with my english ! I try : when my test say that there is an mistake, I would like *stop" the program with out any comment and after my text of error I would like go back to my program.
In attachement I would like that after my MSGBOX is display, that KILL stop my programme and go back to TSTDate for re-asking where was the mistake. Gérard. |
|||
01-23-2017, 04:58 PM
Post: #9
|
|||
|
|||
RE: KILL command.
I think I understand now. First, are you using the connectivity kit to develop your program? If so, please copy and paste your code between the # tags on the forum editor (top right side). That will make it much easier for people to cut and paste your code.
You could make a subroutine for the code shown, and call it from a REPEAT END or WHILE END loop in an earlier part of your program. Instead of KILL, you would use RETURN. I could also suggest that you use the drawmenu facility to create a front-end processor for your program (I hope you find this useful): Code:
|
|||
01-23-2017, 07:13 PM
Post: #10
|
|||
|
|||
RE: KILL command.
Thank DrD !
Double thank for the "Vive la France". I give my program for you see. I will studie your code for me programing. It is of course a good idea and loops you sugest and what I dont' have my way to did. Code:
Gérard. |
|||
01-23-2017, 07:26 PM
Post: #11
|
|||
|
|||
RE: KILL command.
You're very welcome. I use that framework a lot, and I hope it might be of use for you. Being able to select activities via soft keys can be very efficient. So good luck ...
-Dale- |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 4 Guest(s)