I propose identifying the GUI tool kit used during build in the about window as part of the version string.
- "This is SolveSpace version 3.2~e6e5c03e-QT."
- "This is SolveSpace version 3.2~e6e5c03e (QT)."
- "This is SolveSpace version 3.2~e6e5c03e-GTK."
- Additional line: "This build should be identified as 'SolveSpace 3.2~e6e5c03e-QT' when reporting bugs."
When the new version gets widely distributed, depending on how SS was obtained, the user may not know which toolkit GUI they are using.
This is partially a packaging issue, but I think it would help avoid wasted time (for the devs) to help guide the user to report which GUI they are actually using when reporting bugs or asking questions.
I plan to offer AppImages for both versions, since the AppImage will be a single executable and installation will not be necessary. There's no reason to be limited to one or the other. (For devs, this provides easy access to both builds for testing)
Thoughts/suggestions/comments?
I propose identifying the GUI tool kit used during build in the about window as part of the version string.
When the new version gets widely distributed, depending on how SS was obtained, the user may not know which toolkit GUI they are using.
This is partially a packaging issue, but I think it would help avoid wasted time (for the devs) to help guide the user to report which GUI they are actually using when reporting bugs or asking questions.
I plan to offer AppImages for both versions, since the AppImage will be a single executable and installation will not be necessary. There's no reason to be limited to one or the other. (For devs, this provides easy access to both builds for testing)
Thoughts/suggestions/comments?