Skip to content
Snippets Groups Projects
Select Git revision
  • dailybuild_linux-x64
  • dailybuild_win32
  • master default protected
  • sqlite
  • rip_abstraction
  • dailybuild_macos-armv8
  • dd_file_lister_filanem_in_desc_color
  • mode7
  • dd_msg_reader_are_you_there_warning_improvement
  • c23-playing
  • syncterm-1.3
  • syncterm-1.2
  • test-build
  • hide_remote_connection_with_telgate
  • 638-can-t-control-c-during-a-file-search
  • add_body_to_pager_email
  • mingw32-build
  • cryptlib-3.4.7
  • ree/mastermind
  • new_user_dat
  • sbbs320d
  • syncterm-1.6
  • syncterm-1.5
  • syncterm-1.4
  • sbbs320b
  • syncterm-1.3
  • syncterm-1.2
  • syncterm-1.2rc6
  • syncterm-1.2rc5
  • push
  • syncterm-1.2rc4
  • syncterm-1.2rc2
  • syncterm-1.2rc1
  • sbbs319b
  • sbbs318b
  • goodbuild_linux-x64_Sep-01-2020
  • goodbuild_win32_Sep-01-2020
  • goodbuild_linux-x64_Aug-31-2020
  • goodbuild_win32_Aug-31-2020
  • goodbuild_win32_Aug-30-2020
40 results

inkey.cpp

Blame
    • Rob Swindell's avatar
      0d281709
      Rename sbbs_t::ungetstr() and JS console.ungetstr() to ungetkeys() · 0d281709
      Rob Swindell authored
      ... since these methods only feed the keyboard buffer.
      
      Add an optional 'insert' argument to console.ungetkeys() - default is false
      (append).
      
      Add a new version of console.ungetstr() which feeds the passed characters
      directly to the receive input buffer. Now returns bool indicating success.
      Existing scripts (if any) that use console.ungetstr() should continue to work
      just fine.
      
      This is anticipation of telgate.js being able to stuff strings (e.g. username,
      password) into the input buffer and those chars/keys being passed to the
      remote (gatewayed) telnet server. Since the telnet gateway reads directly from
      the receive input buffer (ignoring the keyboard buffer), we needed a way to
      stuff strings of characters into the receive input buffer directly and that
      sort of exposed the weirdness of the existing console.ungetstr() method:
      - it didn't return a return value (not indication of failure)
      - it didn't support an 'insert' operation (even though the underlying C++
        method does)
      - it didn't use the sbbs_t method that already existed for feedding a string
        of characters into the input/keyboard buffer
      0d281709
      History
      Rename sbbs_t::ungetstr() and JS console.ungetstr() to ungetkeys()
      Rob Swindell authored
      ... since these methods only feed the keyboard buffer.
      
      Add an optional 'insert' argument to console.ungetkeys() - default is false
      (append).
      
      Add a new version of console.ungetstr() which feeds the passed characters
      directly to the receive input buffer. Now returns bool indicating success.
      Existing scripts (if any) that use console.ungetstr() should continue to work
      just fine.
      
      This is anticipation of telgate.js being able to stuff strings (e.g. username,
      password) into the input buffer and those chars/keys being passed to the
      remote (gatewayed) telnet server. Since the telnet gateway reads directly from
      the receive input buffer (ignoring the keyboard buffer), we needed a way to
      stuff strings of characters into the receive input buffer directly and that
      sort of exposed the weirdness of the existing console.ungetstr() method:
      - it didn't return a return value (not indication of failure)
      - it didn't support an 'insert' operation (even though the underlying C++
        method does)
      - it didn't use the sbbs_t method that already existed for feedding a string
        of characters into the input/keyboard buffer