Posted by Barbara Brazil on April 20, 2009 at 11:32:43:
In Reply to: f3/f10 and qenditor posted by Marc Shevick on April 20, 2009 at 09:43:04:
Marc:
Where the user is taken following QENDITOR or F3/F10 is determined by the value of RUNSTATE. The meaning of each value of RUNSTATE is documented in the QMONITOR source at line 421. I ran some tests and saw that F3/F10 causes Comet to set RUNSTATE to 0. Other than trapping the F3/F10 and non-fatal errors in each of your programs the only way I can see for you to change the default behavior is to modify QMONITOR. You might try handling the case of RUNSTATE = 0 by attempting to reread the password record (get the password by using the PASSWORD verb) and then running the program from SECPROG$ in the password record. Be careful, though, because QMONITOR will also set RUNSTATE to 0 if there's a problem with the security file. You could get yourself in an endless loop.
While we don't recommend custom QMONITORs because of the inconvenience when a new REL is installed, if this is a problem that others are having and you do make a version of QMONITOR that is a better solution than what we have now, post it on the forum. If the consensus is to use your changes, we will do that.
bb
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.