TZUTC: -0800   
   MSGID: 51480.syncprog@1:103/705 2bfb7b3b   
   REPLY: 51479.syncprog@1:103/705 2bfb6780   
   PID: Synchronet 3.20c-Linux master/b31f84a5d Jan 21 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/1fb16776d Jan 22 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: console.inactivity_warning in JS   
     By: Nightfox to Digital Man on Sat Jan 25 2025 02:18 pm   
      
    >   Re: ctrl/sbbs.ini src/sbbs3/answer.cpp getkey.cpp inkey.cpp js_console.cpp   
    >   By: Rob Swindell (in GitKraken) to Git commit to main/sbbs/master on Fri   
    > Mar 17 2023 07:26 pm   
    >   
    >  RS> - Removed JS console.inactivity_warning   
    >   
    > I'm curious why this was removed?  I may actually have a use for it in   
    > DDMsgReader.   
    >   
    >  RS> MaxSessionInactivity (default: none/unlimited) - Each configured   
    >  RS> external program/door in SCFG can have its own maximum inactivity   
    >  RS> setting (or else the session max inactivity is applied)   
    >   
    > Was console.inactivity_warning removed  because of this change?   
      
   No, the configurable warning duration was changed from being a number of   
   seconds value (which was problematic in some cases) to being a percentage of   
   the maximum inactivity. I could calculate the configured warning duration and   
   make that a read-only property, if that'd be useful.   
      
    > DDMsgreader   
    > could be set up as a loadable module, where there is no setting for a   
    > maximum inactivity.  In that case, it seems to be using the inactivity   
    > setting which I believe is configured in SCFG > System > Advanced Options >   
    > Maximum User Inactivity?   
      
   If "it" is console.getkey() and getstr(), yeah.   
      
    > I had some custom input logic I wrote for DDMsgReader years ago, before   
    > KEY_PAGEUP and KEY_PAGEDN were added to key_defs.js.  Since those are there   
    > now, I am considering using console.getkey() instead of my own input   
    > function. One thing I'm running into is that after the 'Are you really   
    > there?' text is displayed and I press a key, the display of things gets a   
    > bit wonky in DDMsgreader, like the cursor has moved which has pushed things   
    > around a bit. I'm thinking if I had a way to detect that the 'Are you   
    > there?' warning was displayed, maybe I could refresh the screen to make it   
    > look proper again.   
      
   You could override the AreYouThere text.dat string to maybe execute some JS   
   code that does what you need/want?   
      
    > For instance, I made a few screenshots:   
    > Reading a message, before the 'are you there' text (looks good):   
    > http://www.digitaldistortionbbs.com:81/synchronet_stuff/reading1.png   
    > 'Are you really there?' - Still looks okay:   
    > http://www.digitaldistortionbbs.com:81/synchronet_stuff/reading2.png   
    > Then when I press a key, things get a bit wonky - It looks like everything   
    > gets pushed up a few lines:   
    > http://www.digitaldistortionbbs.com:81/synchronet_stuff/reading3.png   
      
   I'm not surprised since DDMsgReader is a "full screen" type script. You could   
   either set the AreYouThere text.dat string to blank, in which case the   
   InactivityAlert text.dat string is sent instead (just some beeps as I recall),   
   or replace AreYouThere with something that works better for a full screen   
   script.   
   --    
                                               digital man (rob)   
      
   Rush quote #41:   
   Angels and demons dancing in my head, lunatics and monsters underneath my bed   
   Norco, CA WX: 60.9øF, 45.0% humidity, 5 mph S wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426