Jump to content
You must now use your email address to sign in [click for more info] ×

Math Functions Not Working?


Recommended Posts

Interesting. They will work if entered as part of an expression. That is, "*sqrt(2)" works, but "sqrt(2)" doesn't. Both work in Designer 1.6.5.123.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

4 minutes ago, Mark Ingram said:

That's because it's an operation on the existing value (i.e. value * sqrt(2)). In theory sqrt(2) should produce a constant number too.

Right. Mainly I tried the expression to prove that sqrt(2) was working at least some of the time. In AD 1.6.5 entering "sqrt(2)" as a value produces 1.414 but in 1.7 it is ignored and the original value is restored.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

1 minute ago, walt.farrell said:

Right. Mainly I tried the expression to prove that sqrt(2) was working at least some of the time. In AD 1.6.5 entering "sqrt(2)" as a value produces 1.414 but in 1.7 it is ignored and the original value is restored.

Ah OK, that's defo a bug then. I thought @JET_Affinity was expecting "value * sqrt(2)" as the result from "sqrt(2)" input.

Link to comment
Share on other sites

21 hours ago, Mark Ingram said:

Ah OK, that's defo a bug then. I thought @JET_Affinity was expecting "value * sqrt(2)" as the result from "sqrt(2)" input.

Interesting. So sqrt(2) returns a 'constant' value, so independent on the current value of a textbox.

But how does this relate to a textbox, like width or height, set to '50%'? (When entering 50% the %, instead of sqrt(2) ís dependent on the current value since it returns 0.5 * value. Which is actually a pretty great feature btw), so that seems to be a different approach?

 

Link to comment
Share on other sites

1 minute ago, Friksel said:

Interesting. So sqrt(2) returns a 'constant' value, so independent on the current value of a textbox.

Why would it return anything else? The value of sqrt(2) is a constant.

Quote

But how does this relate to a textbox, like width or height, set to '50%'? (When entering 50% the %, instead of sqrt(2) ís dependent on the current value since it returns 0.5 * value. Which is actually a pretty great feature btw)

Since 50% represents a proportion rather than an absolute value, it has to be a proportion of something! That ‘something’ can either be another value — e.g. w or h or sqrt(2) — or the current value in the selected input box.

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.4.1 (iPad 7th gen)

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.