|
|
|
|
|
Frequently Asked Question
|
|||||||||||||||||||||
|
When you are compiling a single module in VGER or in LIST.EDIT, the error message should remain until responded to. If there is no error, there is no pause, and the compile message will flash by. I did this for two reasons, (1) save time, and (2) save time. I hate waiting for informational messages, or having to respond when there is nothing amiss. If there is an error, it should wait for you, but if no error, it continues without pause. Do you think I should have the pause? I used to have one, but "BAS ALL" took forever when doing 600 programs. That's 10 minutes waiting time alone. When you are compiling a list of programs, I didn't want to require intervention or delay on every error. In the case of a multiple line compile, like "BAS 1-30 or BAS ALL", all errors are trapped and a special list named ERROR.LIST is created in your list of lists. The errors that were trapped are put into each program's comment record. To view the error list, in LPR type "E ERROR.LIST". If you are in LIST.EDIT, type "GO ERROR.LIST" It will only contain the ones with errors. Clicking on the comment part of the display will take you into the comment record itself to view the actual errors.
No, I don't mind the request at all. I appreciate the input. As I said on the phone, the toolbox has been in development since 1985, but only on the market for less than a year. The more I can help you, the better the product gets. If you have any suggestions, please let me know. I am sure I have blind spots because of familiarity, having been working with and on it since the middle of the 80's. |
||||||||||||||||||||||
|
|
Copyright 2004 DmCons, Inc. All rights reserved. | ||||||||||||||||||||
