Synchronet now requires the libarchive development package (e.g. libarchive-dev on Debian-based Linux distros, libarchive.org for more info) to build successfully.

  1. 22 May, 2021 1 commit
  2. 19 May, 2021 2 commits
    • Deucе's avatar
      679800f7
    • Deucе's avatar
      Use display aspect ratio, not pixel for tracking. · a5c619fc
      Deucе authored
      People are used to thinking about the aspect ratio of displays and
      used to not thinking at all about that of pixels.  Most of the modes
      are simplt 4:3 modes and the text area is the entire window.  The
      only oddball here is the Commodore 64 and 128 40-column modes.
      Because they have a border around them that's wider on the sides than
      the top/bottom, the display aspect ratio is actually narrower than
      a normal NTSC screen (6:5).  It seems the PAL version actually has
      square pixels, but nobody has asked for a PAL Commodore mode, and I
      think that has a different colour palette too so I'm not doing it.
      
      Just to frustrate DigitalMan a bit, the default custom aspect ratio
      is now 4:3 (but can be configured).  At present, modifying the custom
      mode while *in* the custom modes "works", which no sane person would
      want when adjusting the aspect ratio.
      a5c619fc
  3. 18 May, 2021 2 commits
  4. 15 May, 2021 1 commit
  5. 14 May, 2021 2 commits
  6. 16 Aug, 2020 1 commit
  7. 27 Jun, 2020 1 commit
  8. 01 Apr, 2020 2 commits
  9. 25 Jul, 2019 1 commit
  10. 20 Oct, 2018 2 commits
    • deuce's avatar
      7fa0ead9
    • rswindell's avatar
      Change the C128 screen modes (C128_40X25 and C128_80x25) to use the C64 · 301a6260
      rswindell authored
      palette. I can only assume this was a typo? I'm also guessing this is the
      same change that Payton Byrd made in his fork of SyncTERM (he erroneously
      called 2.0), which I haven't been able to locate on github (anyone?). This
      change makes SyncTERM (in C128 modes) appear more consistent with CGTerm.
      
      With this change, I now see no difference between the C64_40X25 screen mode
      and the C128_40X25 screen mode. (Deuce?)
      
      I also have questions about the changes in some of the colors between
      40 and 80 columns modes expressed here (but not observed with CGTerm):
      https://www.commodore.ca/manuals/128_system_guide/app-i.htm
      (e.g. 129 is supposedly green in 40 column mode and dark purple in 80 cols).
      see also: 149, 151, and 159 - if this is true, then another palette
      is needed for C128-80 mode but doesn't explain CGTerm's behavior
      (the colors are the same in 40 and 80 column modes).
      
      Also, the C64 palette changed pretty drastically since SyncTERM 1.0 where
      the colors weres dull/muted and are now bright. And the initial attribute is
      Blue on Grey (not black) - that wasn't the case with v1.0.
      301a6260
  11. 15 Feb, 2018 1 commit
  12. 13 Feb, 2018 1 commit
    • deuce's avatar
      Beginnings of a massive ciolib overhaul... · 210cc022
      deuce authored
      We're switching to TrueColor now, and maintaining a 65536 entry palette
      for the various palettized bits.  This change hurts the overlay output most
      since it currently means floating point calculations for every pixel.
      
      The getfont() function now takes a fontnum argument so you can get all the
      current fonts.
      
      The vmem array now holds the font data, so once a glyph is written to the
      screen, it can stay in that font "forever".  This still has some issues
      with savescreen()/restorescreen() since there's no extension to grab the new
      stuff... that'll be coming soon, likely replacing the pgettext() and
      pputtext() functions.  For now, various popups will likely reset fonts to
      the default font on the screen.
      
      Now that we have all this, the status bar in SyncTERM can retain the default
      font and colours at all times.  Further, menus can be displayed in the "right"
      colours and fonts, and no more translation will be needed.  This is a work
      in progress though, so there's likely to be glitches.  The scrollback doesn't
      have the font data either (same issue as savescreen()/restorescreen()).
      210cc022
  13. 07 Feb, 2018 2 commits
  14. 06 Feb, 2018 1 commit
    • deuce's avatar
      Massive cursor rework... · 0def45be
      deuce authored
      Baiscally, fix all the cursor things.  I'm frankly amazed this ever worked.
      While we're changing everything, remove pointless arguments from some functions.
      Some were ignored, and some only had one possible value.
      0def45be
  15. 05 Feb, 2018 1 commit
  16. 01 Feb, 2018 1 commit
  17. 31 Jan, 2018 1 commit
    • deuce's avatar
      Update to XTerm 256-color palette by default · b09b2dba
      deuce authored
      Use C64 palette from CTerm
      Switch drawrect to use 32-bit pixels
      Put the colour palette index into the screen array, not the attribute palette one
      Remove dac_colors from video_stat structure
      b09b2dba
  18. 15 Jul, 2015 1 commit
    • rswindell's avatar
      Fix link problem introduced in rev 1.18 (Jul-5-2015): · 043cc9ea
      rswindell authored
      When built withOUT the preprocessor macro WITH_SDL defined, ciolib.h doesn't
      include gen_defs.h (perhaps it should), so the use of FREE_AND_NULL in this
      file become function calls and the symbol is not found when linking.
      This is why jsexec was not included in recent daily dev builds of v3.16.
      043cc9ea
  19. 05 Jul, 2015 1 commit
    • deuce's avatar
      Improve the locking "stuff"... · 4d70127d
      deuce authored
      For regular vstatlock things, only hold the lock long enough to copy the
      variables that will be used.
      
      For vstat.vmem stuff, create a separate reference-counting vmem structure
      and a new vmem_lock so the memcpy() of the vmem won't block basic vstat
      accesses.
      
      This appears to fix the recently-added "blockiness" of screen updates in
      SyncTERM, without risking deadlocks or unlocked accesses... the major issue
      holding up a release.
      4d70127d
  20. 03 Apr, 2015 1 commit
  21. 27 Feb, 2015 1 commit
  22. 26 Feb, 2015 1 commit
  23. 10 Feb, 2009 1 commit
    • deuce's avatar
      Various changes around more EGA/VGA capabilities, specifically: · e44ec674
      deuce authored
      1) The ability to make attribute bit three select a second character set
      2) The ability to make the blink attribute toggle background intensity
      3) The ability to make attribute bit three NOT select high intensity
      4) More control over the cursor than just three constants
      
      CTerm support to follow using private set mode parameters.
      e44ec674
  24. 05 Feb, 2008 1 commit
  25. 19 Jan, 2008 2 commits
  26. 15 Oct, 2007 1 commit
  27. 10 Oct, 2007 1 commit
  28. 27 May, 2007 1 commit
  29. 25 May, 2007 2 commits
    • deuce's avatar
      Fix more typos. · 21886f0f
      deuce authored
      21886f0f
    • deuce's avatar
      Add C64 and C128 video modes and palettes. · 6f64d2b3
      deuce authored
      Current;y, I'm useing the PC palette for C128 modes since the documentation
      I found on the C128 said that it used CGA monitors (which were digital)
      
      Can someone clarify this (ie: Did the Commodore monitor use the C64 palette)
      6f64d2b3
  30. 20 Nov, 2005 1 commit
  31. 18 Nov, 2005 1 commit
  32. 22 Oct, 2005 1 commit