1. Forum
  2. Fidonet
  3. SYNC PROGRAMMING

  • src/syncterm/term.c

    From Deucе@1:103/705 to Git commit to main/sbbs/master on Sun Jun 7 22:31:03 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/a44a81fca9fe696ff5fac317
    Modified Files:
    src/syncterm/term.c
    Log Message:
    Fix reading of PBM P4 files

    If the width is not a multiple of eight, ignore the last padding bits
    at the end of each line.

    But really, there's no reason to create a PBM where the width isn't
    a multiple of eight.

    Fixes issue reported by DigitalMan on Discord
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to Git commit to main/sbbs/master on Fri Jun 19 18:41:38 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/1867df03936a69dfd5dfe1dd
    Modified Files:
    src/syncterm/term.c
    Log Message:
    Fix big in parsing binary PBM/PPMs

    Only a single whitespace is allowed between the header and the raster
    data.

    While we're here, remove some unused variables.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to Git commit to main/sbbs/master on Fri Jun 26 10:16:48 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/8e92a64682904c7f3210751a
    Modified Files:
    src/syncterm/term.c
    Log Message:
    Actually hook up lf_expand
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to Git commit to main/sbbs/master on Mon Jul 13 14:04:41 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/bc7374d01c25c85883f9f521
    Modified Files:
    src/syncterm/term.c
    Log Message:
    Fix SGR pixel mouse coordinate origin

    DECSET 1016 reports one-based pixel coordinates, but the conversion
    from ciolib's zero-based high-resolution mouse position subtracted the one-based cterm origin directly. This removed one full character cell
    from each axis and could report zero or negative coordinates near the
    top or left edge.

    Use the zero-based pixel origin implied by the one-based cterm cell
    origin instead, and treat high-resolution coordinates as present only
    when both axes are non-negative. This keeps valid zero-valued pixels
    from being mistaken for missing data while preserving the text-coordinate fallback for backends that do not provide pixel positions.

    Fixes SourceForge ticket 267.

    Co-Authored-By: OpenAI Codex <noreply@openai.com>
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)