Is your feature request related to a problem? If so, please describe.
No response
What is your new feature idea or request?
Real-world RPO software has a separate window for prompts that are programmed to show up at predefined points during the scenario. For example:
CALL AS ACK17 AND POINT OUT N123 (10 NE OF BOS, CODE 1234) DESCENDING INTO KPSM. IF APPROVED, EXECUTE COMMANDS:
N123 DM 3000 EXP
N123 WAIT 10 HO B1Z
N123 WAIT 20 A
N123 AT KPSM DEL
As the RPO, you can just right-click on the prompt and it will open a right-click menu with the following options:
• “Execute / Mark Completed”: Any programmed commands (such as the 4 in the example prompt above) will auto-execute and the prompt will delete.
• “Execute / Mark Completed All”: Same thing, but with all pending prompts instead of just the current one.
• “Delete”: Deletes the prompt without executing commands (for example, if the student unables the point out or the instructor decides not to call it)
I’ve currently been using SAY commands to incorporate prompts into my scenarios, but this is not ideal because (1) it’s easy for prompts to get buried with all of the other things in the command line and (2) the instructor has to manually enter any commands associated with the prompt.
Is your feature request related to a problem? If so, please describe.
No response
What is your new feature idea or request?
Real-world RPO software has a separate window for prompts that are programmed to show up at predefined points during the scenario. For example:
CALL AS ACK17 AND POINT OUT N123 (10 NE OF BOS, CODE 1234) DESCENDING INTO KPSM. IF APPROVED, EXECUTE COMMANDS: N123 DM 3000 EXP N123 WAIT 10 HO B1Z N123 WAIT 20 A N123 AT KPSM DEL
As the RPO, you can just right-click on the prompt and it will open a right-click menu with the following options: • “Execute / Mark Completed”: Any programmed commands (such as the 4 in the example prompt above) will auto-execute and the prompt will delete. • “Execute / Mark Completed All”: Same thing, but with all pending prompts instead of just the current one. • “Delete”: Deletes the prompt without executing commands (for example, if the student unables the point out or the instructor decides not to call it)
I’ve currently been using SAY commands to incorporate prompts into my scenarios, but this is not ideal because (1) it’s easy for prompts to get buried with all of the other things in the command line and (2) the instructor has to manually enter any commands associated with the prompt.