1. Forum
  2. DOVE-Net
  3. Synchronet Programming

  • src/xpdev/genwrap.c

    From Deucе@VERT to Git commit to main/sbbs/master on Thursday, October 09, 2025 16:02:28
    https://gitlab.synchro.net/main/sbbs/-/commit/1ea96df1b6d05d2730dd2a24
    Modified Files:
    src/xpdev/genwrap.c
    Log Message:
    Add support for NO_OS_VERSION

    This allows avoiding needing ini_file.c, strlist.c, etc. for things
    that use xpdev by just building select files.

    Otherwise you end up with a linking error. due to not finding
    iniReadFile().

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Monday, January 05, 2026 00:49:23
    https://gitlab.synchro.net/main/sbbs/-/commit/4067f32824605ad984122488
    Modified Files:
    src/xpdev/genwrap.c
    Log Message:
    duration_estimate_to_[v]str(): Don't include ".0" suffix for value of zero

    When a unit value > 1 was specified, we could get strings with extra "noise" (e.g. "0.0h" with the upcoming change to minutes_to_str()).

    This does sort of ignore the 'precision' argument in this case, but we already do (provide no fraction) for exactly-divisible values (e.g. 60min = "1h"). So if we ever uses these functions to provide columns with aligned decimals, that might be a problem.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Windows 11)@VERT to Git commit to main/sbbs/master on Friday, January 09, 2026 22:26:15
    https://gitlab.synchro.net/main/sbbs/-/commit/0a26d710549f9651895bb392
    Modified Files:
    src/xpdev/genwrap.c
    Log Message:
    Beautify output of duration estimate string functions

    duration_estimate_to_vstr() would sometimes output plural suffixes for values of "1", e.g. "1 minutes", "1 hours" when the value was not an exact multiple (and depending on the precision argument value).

    Both duration_estimate_to_str() and duration_estimate_to_vstr() would report (depending on precision argument) values of "1.0 units" when the value is actually greater than "1.0" (by some fraction) and actual 1.0 units would be reported at "1 unit". It turns out, it's really not easy to predict the output of printf("%f") with different precision values using math, so just check the printf() output and adjust accordingly.

    Demonstration of the fixed problems using the possible parameter values
    to JS system.secondstr() and system.minutestr() with duration values 59, 60, and 61:
    '00:00:59' '59' '59m' '59m' '59 minutes' '59 minutes'
    '00:01:00' '1:00' '1h' '1h' '1 hour' '1 hour'
    '00:01:01' '1:01' '1.0h' '1h 1m' '1.0 hours' '1 hours 1 minute'

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net