Maths operation in panels

[Subpath]

@VectorStyler, @Devil-Dinosaur

Seems it works only with Integer Values
i test it in Transform Panel with Scale and Position

so 564 + 200 will work
and 564,5 + 200 not

[VectorStyler]

@Subpath The issue could be with the decimal character, use '.'

[b77]

@VectorStyler Here it works when '+10' overwrites the highlighted value:

When the value is not highlighted, it doesn't work:

[Subpath]

@VectorStyler

indeed works with 622.3 + 200
and not with 622,3 + 200

but i doesnt set the decimal char
VS did it

btw in my tests i used "pt"

[Devil Dinosaur]

@Subpath said in Maths operation in panels:

@VectorStyler

indeed works with 622.3 + 200
and not with 622,3 + 200

but i doesnt set the decimal char
VS did it

btw in my tests i used "pt"

Yes, I just tried and it seems it brings some changes with dot as a separator instead of the comma. But the result is not accurate (?) : 90+10 becomes 265,118 (movie here).
I will do some other tries, it may be some issue with Mac Sonoma and it's keyboard settings.

[VectorStyler]

@b77 said in Maths operation in panels:

When the value is not highlighted, it doesn't work:

The problem is with the "pt" in the middle of that expression.

[VectorStyler]

@Devil-Dinosaur said in Maths operation in panels:

But the result is not accurate (?)

The "mm" in the middle of the expression causes the problems.

[Devil Dinosaur]

OK it works but I have 2 actions to execute : changing "," comma into "." dot and erase mm (writing the operation before mm doesn't work).
Is there a way in VS to change the decimal to "." (or is it something to do in the Sonoma?).

[VectorStyler]

@Devil-Dinosaur I will try to fix these

[Subpath]

@Devil-Dinosaur, @VectorStyler

I'm wondering too.
Because everywhere I've looked in VS the "," char is used. (Win 10)
If mathematical operations in value fields only work with the character “.”
Then I think VS should be able to change the "," to "." somewhere in the settings.
Or convert that char in general.

[VectorStyler]

@Subpath Such a conversion happens for numbers, but not for expressions.

The problem is that starting from 1.2 expressions can also be used with number variables to create dynamic values for these types for number fields, and these expressions are stored in the document.

Moving such a document from one computer to another will cause problems with the expressions.
So currently the expression parser uses "."

Also, the comma ',' character may be used in such expressions as parameter separator. So we cannot just convert it.
This is why all programming languages use "." for decimal separators regardless of system settings.

This is a problem I have to figure out in VS.

[Devil Dinosaur]

@VectorStyler
Works fine now, thanks.