Hello all,
I've been playing around with display files that are shown to a caller when they start a Door app, before the app actually starts. This is done by creating the display file and putting it in /sbbs/text/menu/xtrn. In my example, I've made the file 'usurper.msg' and put it in that directory.
When starting the Usurper door, that file displays as expected. But, after it displays there's a prompt there to "Hit any key". When you do that, it proceeds to start the door, again as expected. I'd like that "Hit any key" prompt to not happen. I've put "@POFF@" at the top of that display file but it seems to have no effect. What is causing the prompt? Any way to disable that from happening? Thanks for info.
Digital Man wrote to Gamgee <=-
Re: Display files for XTRN doors
By: Gamgee to All on Mon Jul 21 2025 09:24 pm
I've been playing around with display files that are shown to a caller when they start a Door app, before the app actually starts. This is done by creating the display file and putting it in /sbbs/text/menu/xtrn. In my example, I've made the file 'usurper.msg' and put it in that directory.
When starting the Usurper door, that file displays as expected. But, after it displays there's a prompt there to "Hit any key". When you do that, it proceeds to start the door, again as expected. I'd like that "Hit any key" prompt to not happen. I've put "@POFF@" at the top of that display file but it seems to have no effect. What is causing the prompt? Any way to disable that from happening? Thanks for info.
Most likely, it's a screen-clear sequence that's following the display
of your file. You can either: set clear_screen_on_exec=false in the [xtrn_sec] or [xtrn:usurper] section of your ctrl/modopts.ini file, or
add {at}RESETPAUSE{at} code to the end of your display file. One or
either of those should do the trick.
The screen clear I'm suspecting comes from the exec/prextrn.js file.
Digital Man wrote to Gamgee <=-
Re: Display files for XTRN doors
By: Gamgee to All on Mon Jul 21 2025 09:24 pm
I've been playing around with display files that are shown to a caller when they start a Door app, before the app actually starts. This is done by creating the display file and putting it in /sbbs/text/menu/xtrn. In my example, I've made the file 'usurper.msg' and put it in that directory.
When starting the Usurper door, that file displays as expected. But, after it displays there's a prompt there to "Hit any key". When you do that, it proceeds to start the door, again as expected. I'd like that "Hit any key" prompt to not happen. I've put "@POFF@" at the top of that display file but it seems to have no effect. What is causing the prompt? Any way to disable that from happening? Thanks for info.
Most likely, it's a screen-clear sequence that's following the display of your file. You can either: set clear_screen_on_exec=false in the [xtrn_sec] or [xtrn:usurper] section of your ctrl/modopts.ini file, or add {at}RESETPAUSE{at} code to the end of your display file. One or either of those should do the trick.
I found the 'clear_screen_on_exec=false' already in my [xtrn_sec]. I created the [xtrn:usurper] section and added that phrase there, but it didn't help. Adding {at}RESETPAUSE{at} (using the proper @'s) to the display file didn't do anything (also tried POFF and NOPAUSE).
The screen clear I'm suspecting comes from the exec/prextrn.js file.
I even commented out these lines from that file:
if (options.clear_screen_on_exec) {
console.clear();
}
And that also didn't change anything. This isn't a HUGE problem, but
seems strange that it can't be changed...
Re: Re: Display files for XTRN doors
By: Gamgee to Digital Man on Tue Jul 22 2025 08:45 am
I've been playing around with display files that are shown to a caller when they start a Door app, before the app actually starts. This is done by creating the display file and putting it in /sbbs/text/menu/xtrn. In my example, I've made the file 'usurper.msg' and put it in that directory.
When starting the Usurper door, that file displays as expected. But, after it displays there's a prompt there to "Hit any key". When you do that, it proceeds to start the door, again as expected. I'd like that "Hit any key" prompt to not happen. I've put "@POFF@" at the top of that display file but it seems to have no effect. What is causing the prompt? Any way to disable that from happening? Thanks for info.
Most likely, it's a screen-clear sequence that's following the display of your file. You can either: set clear_screen_on_exec=false in the [xtrn_sec] or [xtrn:usurper] section of your ctrl/modopts.ini file, or add {at}RESETPAUSE{at} code to the end of your display file. One or either of those should do the trick.
I found the 'clear_screen_on_exec=false' already in my [xtrn_sec]. I created the [xtrn:usurper] section and added that phrase there, but it didn't help. Adding {at}RESETPAUSE{at} (using the proper @'s) to the display file didn't do anything (also tried POFF and NOPAUSE).
Did you add the RESEPAUSE code to the *end* of the display file?
The screen clear I'm suspecting comes from the exec/prextrn.js file.
I even commented out these lines from that file:
if (options.clear_screen_on_exec) {
console.clear();
}
And that also didn't change anything. This isn't a HUGE problem, but seems strange that it can't be changed...
It is strange. Are you sure the copy of the prextrn.js file you're modifying is getting executed? Maybe try adding some debug output statements (to the terminal or the log) - that might help determine when/why the pause is happening as well.
I have no idea if that prextrn.js file is being executed... At this point I'm gonna just live with it, as I don't know how to add debug output and have been distracted by other things... :-)
Thanks for the help anyway!
Digital Man wrote to Gamgee <=-
Re: Re: Display files for XTRN doors
By: Gamgee to Digital Man on Tue Jul 22 2025 03:33 pm
I have no idea if that prextrn.js file is being executed... At this point I'm gonna just live with it, as I don't know how to add debug output and have been distracted by other things... :-)
Thanks for the help anyway!
I took a second look at that prextrn.js script (which I didn't write)
and finally noticed the hard-coded call to console.pause(), which is
the pause you're seeing. I added a new module option (pause_after_info) which you can now set to false to disable that behavior.
| Sysop: | Luis Silva |
|---|---|
| Location: | Lisbon |
| Users: | 764 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 145:35:26 |
| Calls: | 331 |
| Calls today: | 1 |
| Files: | 46,971 |
| Messages: | 13,118 |