Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dailybuild_linux-x64
  • dailybuild_win32
  • 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

con_out.cpp

Blame
    • rswindell's avatar
      1b14e744
      So Nelgin noticed that in novice (non-expert) menu mode, the A/S/D cmds · 1b14e744
      rswindell authored
      from the Chat menu would immediately clear the screen and redisplay the
      menu after displaying the change in the node's state. This was due to the
      enhancement in rev 1.77 of con_out.cpp whereby we no longer increment
      lncntr if the first lines displayed after a key-press are blank (who
      cares if blank lines scroll off the screen?). That's fine and all, but the
      auto-pause check in outchar(FF) would only auto-pause if the line-counter
      was greater than *one* (has been this way since forever). So with the
      enhancement in 1.77, a single non-blank line displayed after a key-press
      was now not enough to trigger the auto-pause ([Hit a Key] prompt).
      So I've changed the line-counter trigger value to greater than *zero*,
      which means we could have some new excessive auto-pauses, but other places
      where auto-pause wasn't working, should again.
      
      One new excessive auto-pause was after the system password was entered at
      the SY: prompt, so that fix is included in this commit.
      1b14e744
      History
      So Nelgin noticed that in novice (non-expert) menu mode, the A/S/D cmds
      rswindell authored
      from the Chat menu would immediately clear the screen and redisplay the
      menu after displaying the change in the node's state. This was due to the
      enhancement in rev 1.77 of con_out.cpp whereby we no longer increment
      lncntr if the first lines displayed after a key-press are blank (who
      cares if blank lines scroll off the screen?). That's fine and all, but the
      auto-pause check in outchar(FF) would only auto-pause if the line-counter
      was greater than *one* (has been this way since forever). So with the
      enhancement in 1.77, a single non-blank line displayed after a key-press
      was now not enough to trigger the auto-pause ([Hit a Key] prompt).
      So I've changed the line-counter trigger value to greater than *zero*,
      which means we could have some new excessive auto-pauses, but other places
      where auto-pause wasn't working, should again.
      
      One new excessive auto-pause was after the system password was entered at
      the SY: prompt, so that fix is included in this commit.