Apply button functions as OK in Spline properties

I just created a spline. I wanted to adjust the control points.

When I click Apply to see the effect of the new values on the spline, though, the button behaves as if I pressed OK, and closes the dialog. I then have to right-click the spline again to open the Properties window.

I suspect this is a bug?

OS: Arch Linux (Wayland, running with QT_QPA_PLATFORM=xcb) Seamly2D Version: 0.6.0.1

Same here. I haven’t used that tool in a while.

Devuan Linux Seamly release date 2026.08.31

@STEELBAS “Version” is basically worthless, what’s your release date?

:unicorn:

It’s already just been reported in another topic. I’m already fixing it.

Oh, I didn’t know that! Well, seems it’s already being fixed, but for what it’s worth:

Seamly2D version: Seamly2D 0.6.0.1
Build revision: unknown
Build date: Built on Wed Sep 2 2026 at 20:17:56
Qt Version: 6.11.2
CPU: x86_64
Compiler: GCC 16.2.1 20260810 64 bit
CPU: x86_64
OS: Linux
OS Version: unknown
Locale: en_US
Country: United States
Language: English
Script Name: Latin
Decimal Point: ,
Negative Sign: -
Positive Sign: +
Direction: Automatic
System Codec: UTF-8
Arguments: seamly2d

Oh, great! I did search for this on the forums, but I wasn’t quite able to find a pre-existing report on it.

Yeah, it’s odd, but the version number hasn’t been advanced for I think several years now. Do you build it yourself? The AppImage has the build date as the version. I don’t know about flatpak.

:unicorn:

I do, and it’s a pain every time :see_no_evil_monkey: I wish someone would add it to a custom user repo for Arch, but oh well.

You’re using quite an old version for a forum Wizard, by the way :sweat_smile: I suspect a typo?

Search only searches the topic titles.

That said - I updated the Interactive Spline dialog… as well as all the dialogs that have formulas. I got rid of all the stupid expand / collapse buttons and replaced them with auto focus when clicking in the text box. .. or as the case is Tab’ing to.

That sounds great, I’m looking forward to trying it out!

If you care I could explain the whole “version” thing… but suffice to say we basically go by the Githbub release version… which is Year.Month.Day.Mins/Secs. There is a script that gets run on Github that overrides the built in 0.6.0.1'. If you build locally the versiom will be 0.6.0.1’ because it’s not running the script that literally rewrites that section of code with the current date in the Github format.

If you look in the Seamly2D/scripts… there is a script called version.sh. In the CI this gets runs first, updates the code, then builds.