Menu

#209 Screen snaps to integer scaling size on connect/disconnect

1.7
closed
None
Win32-GDI
1.7rc2
2025-10-09
2025-10-05
No

x-bit has reported an issue in https://sourceforge.net/p/syncterm/feature-requests/107/ where when the window is resized to a non-integer size, it gets resized to the next smallest integer size on connect and disconnect.

While this sort of thing may be acceptable when wildly changing the output mode (ie: C64), it should certainly behave better than that.

1 Attachments

Discussion

  • Stephen James Hurd

    • status: open --> pending
     
  • Stephen James Hurd

    Ok, I think I have a fix, which should be in the latest nightly now (which is 1.8b). If this works, it will be in 1.7rc3 (and the 1.7 release). @xbitops

    (This is also my first attempt to tag someone in an edit comment... hope the email finds you!)

     
    🎉
    1
  • xbit ops

    xbit ops - 2025-10-05

    1.8b worked like a champ! 100%.

    The tag didn't find my email, but it did link to my profile correctly. Perhaps thats a setting on my profile side.

     
    • Stephen James Hurd

      Excellent, I'll just not tag people anymore since it doesn't do what I had hoped. :D

       
  • Stephen James Hurd

    • status: pending --> closed
     
  • Stephen James Hurd

    This works, added to the 1.7 branch, and bracing for an rc3.

     
    👍
    1
  • xbit ops

    xbit ops - 2025-10-09

    Quick question, you state you're bracing for rc3 but 1.8b is out. Just trying to understand versions so i can post on my x-news rss feed correctly: https://x-bit.org/x-news/

     
    • Stephen James Hurd

      Yeah, I'm thinking I won't do a 1.7rc3, just go directly to the v1.7 release.

      So when I start preparing for an official release, I create a new release branch that will only get bug fixes in it. Once at least a week goes by without any bugs, that becomes an official release and will not have any changes going forward. The release branch is where the official releases come from (rcs and final).

      The alpha and beta builds come from the master branch. If a new feature (rather than a fix) is added in the master branch (encrypted dialing directories in this case) after a release branch has been created, it gets a new minor version (1.8b in this case). Alpha and Beta builds are expected to have problems, and are nebulous versions, so two copies of 1.7b for example may have wildly different features and bugs.

      There have been some builds of 1.8b that will eat your dialing directory... corrupting it to the point where you need to restore from a backup... this is "fine" because it's a beta version (I should really have dropped all the way back to alpha, but I was feeling confident). This would not be fine for a release.

      I hope I included the information you're looking for!

       
      👍
      1

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB