Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 32266  |
|  Gamgee to Digital Man  |
|  Re: Display files for XTRN doors  |
|  22 Jul 25 15:33:54  |
 
TZUTC: -0500
MSGID: 58374.sync_sys@1:103/705 2ce61c74
REPLY: 58373.sync_sys@1:103/705 2ce5e387
PID: Synchronet 3.21a-Linux master/8c7887462 Jul 18 2025 GCC 14.2.0
TID: SBBSecho 3.29-Linux master/6d0371950 Jul 15 2025 GCC 12.2.0
BBSID: PALANTIR
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
Re: Re: Display files for XTRN doors
By: Digital Man to Gamgee on Tue Jul 22 2025 10:25 am
> 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.
> > DM> Most likely, it's a screen-clear sequence that's following the
> > DM> display of your file. You can either: set clear_screen_on_exec=false
> > DM> in the [xtrn_sec] or [xtrn:usurper] section of your ctrl/modopts.ini
> > DM> file, or add {at}RESETPAUSE{at} code to the end of your display
> > DM> 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?
Yes, at the end. Seemed to have no effect.
> > DM> 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!
---
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757
SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 206 317 400 426 428 550 700 705 240/1120 5832 263/1
SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 8912 5054/30
SEEN-BY: 5075/35
PATH: 103/705 280/464 460/58 229/426
|
[ << oldest | < older | list | newer > | newest >> ]