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

bitmap_con.c

Blame
    • Deucе's avatar
      c6a2f44f
      Another large speedup... only update bitmap when drawing a frame · c6a2f44f
      Deucе authored
      Previously, every change would be flushed through to the bitmap, now
      it only flushes before a frame is sent to the driver, or when specific
      things (like setting pixels) occur.
      
      This about doubles the throughput again, running the test at 11
      seconds (started at 179).  At a 16× speedup now from when I started.
      
      This can now display at about 10Mbps, which is still kinda slow,
      but at least it's not completely terrible anymore.
      
      This could likely be improved by better timing of the frame
      generation... it tries to hot 100Hz right now, which is a bit
      excessive.
      c6a2f44f
      History
      Another large speedup... only update bitmap when drawing a frame
      Deucе authored
      Previously, every change would be flushed through to the bitmap, now
      it only flushes before a frame is sent to the driver, or when specific
      things (like setting pixels) occur.
      
      This about doubles the throughput again, running the test at 11
      seconds (started at 179).  At a 16× speedup now from when I started.
      
      This can now display at about 10Mbps, which is still kinda slow,
      but at least it's not completely terrible anymore.
      
      This could likely be improved by better timing of the frame
      generation... it tries to hot 100Hz right now, which is a bit
      excessive.