Jump to content

Unable to create new document in inches with fractions. (5.XXX - 8.XXX)


Recommended Posts

Hey everyone, 

I just downloaded Affinity Designer but can't even get started as it prevents me from creating a page in the desired size. 

I want my page to be 5.125 x 8.25 inches, BUT when typing that, it sets a random number instead.

853.333 instead of 5.125 and then 825 instead of 8.25 (always erasing the dot)

It will not accept any number with fractions !!! I tried comma and dot. Non work. 

Though I can easily create a 5x8, 6x9, 8x10

Anyone experiencing the same issue or can replicate? Thx a lot

 

Edited by NVNDO
Link to comment
Share on other sites

Welcome to the Serif Affinity forums.

Windows, or macOS? What release of the OS?

What kind of keyboard do you use, and what language/regiion do you have specified in your OS?

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

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

Hey there,

Using Windows 10 & Affinity Designer 2 V2.1.1

Using a Spanish keyboard with German layout. I'll try changing the layout and comment in a moment... ...

EDIT:  Changing between layouts does not help. The issue remains. Tried. Ger/Spa, Ger/Ger, Spa/Spa - all give the same result. 

Edited by NVNDO
Link to comment
Share on other sites

Sorry; should have noticed this was a Windows forum, and not asked about macOS.

Thanks for the info about your OS release and the keyboard and OS settings. I can't help with that combination. I do not recall having seen this mentioned, but perhaps someone else will have an idea.

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

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

41 minutes ago, NVNDO said:

853.333 instead of 5.125 and then 825 instead of 8.25

  1. I am curious, though, about one thing. I can understand typing 8.25 and ending up with 825 if it didn't recognize the "." character.

    But it seems inconceivable to type 5.125 and end up with 853.333. First, because the numbers are completely different. Next, because where did that "." come from?
     
  2. Also, are you typing these using the numeric keypad on your keyboard, or using the standard keyboard keys?

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

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

1. Me too... I don´t understand how it comes up with that random number either. 

It always spits out the same (853.333 in) number when entering 3 or more numbers after the dot.

When only placing 2 numbers after the dot, it just erases the dot. 

 

Fun-fact: When changing mm to inch, the first numbers that appear in the boxes for height and width do have (.)s  + multiple numbers after the (.)

 

2. I tried numbers and point on both, numpad and keyboard. 

 

Add-On: trying to record the error since opened the post, but my stupid Windows Game-Bar used to record my screen is not capturing the "New-document-window" and recording with my phone creates a video too large to send by mail in order to post. 

Edited by NVNDO
Link to comment
Share on other sites

Hi @NVNDO,

Welcome to the Affinity Forums :)

This isn't an issue I've seen being reported previously, though I am able to replicate here - when entering 5.125" x 8.25" using an English keyboard language, the correct values are shown and retained by the app. Once changing the keyboard language to German through Windows Settings and using the Numpad keys, I am now seeing the exact same behaviour as yourself.

I cannot entirely explain this behaviour currently, as it does not occur for me when using the top row of number keys, though I will be reporting it to our development team to be resolved asap.

In the meantime, it appears as though copy and pasting values into this dialog retains the correct values as expected.

My screen recording below shows this issue, where I type using the top numbers then numpad in English, switch to German layout and repeat the same - when using 3 decimals or more the value of 853.333 is shown, when using 2 decimals or less the decimal point is ignored:

 
I hope this helps!

Link to comment
Share on other sites

Just to update you, it appears our team have found the cause of this - when using the Numpad Decimal with these different language keyboards it is entered as a comma in the Affinity field, however this comma is not accepted and removed from the value.

The reason that 3 or more decimals becomes '853.333' is because the value entered without the separator (ie 5125) is above the maximum accepted value and therefore this is used instead.

If you use the comma key on your keyboard, rather than the Numpad Decimal key when entering this value, you should hopefully find it works as expected - when using either the top number row or the numpad numbers, with any keyboard language.

In either case, this issue is logged with our team to be resolved as above :)

Link to comment
Share on other sites

Hey @Dan C

Thank you very much for digging into this and trying to find a temporary workaround.

I had already tried using the upper numbers of keyboard and the corresponding point there, but it does not work on German, neither Spanisch keyboard settings. *At least for me...

Btw: I have the comma of Numpad set as a point, as I never use the comma. Though it doesn't work like mentioned above. 

Also installed the English keyboard setting and tried, but it doesn't make a difference. Restarted Affinity Designer and the PC. NO change. 

I eventually tried pasting the values of 5.125 and 8.25 in all three settings , but still, no luck....

 

I'm out of ideas.

I have also tried all possible settings to recording the issue, but the stupid Game-Bar in Windows only records the Affinity background screen, not the actual window in which the project settings are made. Have spend at least 2-3 hours on this for nothing...   What program do you use?

 

...at least I could help getting an unknown issue to be worked on and hopefully solved in a near future.. 

Edited by NVNDO
Link to comment
Share on other sites

I'm sorry to hear this still isn't working for you - as I'm not able to replicate that behaviour here. 

On 7/14/2023 at 3:25 PM, NVNDO said:

Using a Spanish keyboard with German layout

I've not heard of this combination before, is this a physical Spanish layout on the keyboard itself, but you have the language set to German in your OS settings?

6 hours ago, NVNDO said:

Btw: I have the comma of Numpad set as a point, as I never use the comma. Though it doesn't work like mentioned above. 

How specifically have you set this on your machine? As Affinity automatically converts the decimal to a comma when set to certain UI languages, or using certain keyboard languages and this may be conflicting.

6 hours ago, NVNDO said:

I had already tried using the upper numbers of keyboard and the corresponding point there

Do you have a comma or decimal point key near the bottom right (usually around the 'Alt Gr' key) of your keyboard? If so, please try using either of these options - do both of these still fail?

Also just to confirm - I do use OBS for screen recording, but don't require one from yourself currently, thanks for the offer!

Many thanks once again :)

Link to comment
Share on other sites

4 hours ago, Dan C said:

I've not heard of this combination before, is this a physical Spanish layout on the keyboard itself, but you have the language set to German in your OS settings?

Exactly. I'm German, but living in Spain. The Spanish layout makes it super easy to write German with its äüö without having to memorize strange combinations.  That's basically why :)

4 hours ago, Dan C said:

How specifically have you set this on your machine? As Affinity automatically converts the decimal to a comma when set to certain UI languages, or using certain keyboard languages and this may be conflicting.

You can set this in the Region-settings in the CTRL-Panel.

4 hours ago, Dan C said:

Do you have a comma or decimal point key near the bottom right (usually around the 'Alt Gr' key) of your keyboard? If so, please try using either of these options - do both of these still fail?

Yes. They all failed. points, commas, numpad, all layouts and combinations. BUT!! Its seems like all this was due to that setting I had changed. :/

 

I just changed it back to normal and now it works! Jesus.... Seems like I messed that up myself.. I feel somewhat bad - sorry Dan, I didn't want to create unnecessary trouble. 

 

Now all 3 layouts work. 

German - creating a comma at numpad.

Spanish - creating a point at numpad - having to use the comma from above Alt Gr.

My German/Spanisch one - creating a point as well. having to use the comma from above the Alt gr. again. 

 

What a hussle.... 🤦‍♂️

Thank you sooooo much Dan for all your help.

This setting did not even pop up my mind as its months ago when I changed it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.