USER FORUM
(you are viewing a thread; or go back to list of threads)
Release Schedule (by Wink Saville)
Is there a schedule for the next release of Solvespace?
I noticed the last release, 3.1, was June 01, 2022, 3 years ago. I searched the forums and the latest entry mentioning in the results for <release schedule>[1] was April 2023.
-- Wink
[1]: https://solvespace.com/forum.p...;parent=5225&tt=1682143673
I noticed the last release, 3.1, was June 01, 2022, 3 years ago. I searched the forums and the latest entry mentioning in the results for <release schedule>[1] was April 2023.
-- Wink
[1]: https://solvespace.com/forum.p...;parent=5225&tt=1682143673
(no subject) (by Paul)
There is no schedule, but it's been "almost ready" for at least 6 months if not a year. I'm inclined to build a release candidate right now but have just asked the other maintainers if they're OK with that over on github. If there are no objections in the next few days I'd like build RC1 next week. An RC usually gets people to focus on any "must fix" issues prior to the actual 3.2 release.
There is one issue I personally wanted fixed but it only happens on Windows and I have no way to debug and fix it since I only do development on Linux. It's also the reason the text window can be blurry on Windows:
https://github.com/solvespace/solvespace/issues/681
At this point I'm willing to let that one go since it's an existing problem with 3.1 anyway. Other than that it looks like just translation updates, and we can't really hold up a release for those (some have been done).
There is one issue I personally wanted fixed but it only happens on Windows and I have no way to debug and fix it since I only do development on Linux. It's also the reason the text window can be blurry on Windows:
https://github.com/solvespace/solvespace/issues/681
At this point I'm willing to let that one go since it's an existing problem with 3.1 anyway. Other than that it looks like just translation updates, and we can't really hold up a release for those (some have been done).
Blurry text (by Geert Hospers)
I only got the blurry characters on Windows when I downloaded an unofficial prerelease version, some 2 months ago.
In the present official 3.1 I never got blurry characters.
For me it is NOT an existing problem, and I would not be happy with blurry characters in a new version...
I understand that many software developments are done under Linux these days.
But (I think) +90% USERS work with Windows. So please do not let them down with an inferior release.
In the present official 3.1 I never got blurry characters.
For me it is NOT an existing problem, and I would not be happy with blurry characters in a new version...
I understand that many software developments are done under Linux these days.
But (I think) +90% USERS work with Windows. So please do not let them down with an inferior release.
Blurry text (by Geert Hospers)
Addition about blurry text: see my topic Thu May 8 2025, 07:50:45
(no subject) (by Paul)
@Geert Hospers I have the blurry text on Windows using the official 3.1 download. I'm wondering if it only happens on certain versions of windows since it has something to do with the scroll bars, and I don't see it on Linux using Wine. In Wine it uses a very old style scrollbar like Windows XP or older.
happy to help (by dgramop on github)
if we start tagging issues (bugs etc.) for release, I'd be happy to jump on them - I'm eager for solvespace to release!
(no subject) (by Paul)
@dgramop there is only one blocker here:
https://github.com/solvespace/solvespace/milestone/5
It's on Windows only...
I'm happy to do 3.2 RC1 now that the step bug is fixed.
https://github.com/solvespace/solvespace/milestone/5
It's on Windows only...
I'm happy to do 3.2 RC1 now that the step bug is fixed.
(no subject) (by Paul)
Version 3.2 RC1 is available here:
https://github.com/solvespace/solvespace/releases/tag/v3.2-rc1
This release candidate is not going be the final 3.2, there are a few last minute fixes happening.
As usual, this version can read files from older versions. Older versions should be able to read files from 3.2 so long as they don't use any of the new features.
https://github.com/solvespace/solvespace/releases/tag/v3.2-rc1
This release candidate is not going be the final 3.2, there are a few last minute fixes happening.
As usual, this version can read files from older versions. Older versions should be able to read files from 3.2 so long as they don't use any of the new features.
(no subject) (by Ali)
I use SolveSpace on both XUbunutu 24.04 and Windows 10. I have not seen a blurry text window on either operating system. I tried out the release candidate this weekend on Windows 10, too, without observing the blurry window. Looks like the issue comes from adding/removing the scrollbar in the text window. Using one of my parts with ~24 subgroups, I was not able to produce blurry-ness in the text window. I cannot test the release candidate on Windows 11 over this coming week, however, I can test the release from ~12/03/2024. I will report back next weekend if desired.
"Blurry" text bug replication (by MarbleMunkey)
I think I can reproduce the blurry text bug, and can make it go away on the saame system. The change seems to be the Windows system display scaling (Settings -> System -> Display -> Scale). With it set to 100% or 200% it looks fine. If it's set to anything else (125, 150, etc) it looks chunky. It's poor anti-aliasing. It looks exactly like early LCD monitors that didn't handle resolutions that didn't match their exact resolution.
(no subject) (by Paul)
There are two problems on Windows. Both involve the text window being the wrong size. If you click something that causes the scroll bar to appear or disappear, the usable area changes width. The text window is then rendered at the previous width and stretched to fit the window dimensions. This makes the text blurry. Somehow the mouse code gets it right so the buttons at the top right have misaligned click areas. That all gets corrected if you even slightly resize the window. The other problem seems to involve monitor settings other than 100 percent which similarly causes resizing that doesn't look good.
I'd prefer these get fixed for version 3.2 but since they are existing problems we might have to leave them unfixed. The github issue has all the info if anyone wants to try fixing it.
I'd prefer these get fixed for version 3.2 but since they are existing problems we might have to leave them unfixed. The github issue has all the info if anyone wants to try fixing it.
Post a reply to this comment: