Jump to content

Recommended Posts

Posted

 

There is an error in the way parameter values are changed Setup document with the mouse wheel in Windows 11. This applies to an already open document, and if we want to change the Dimensions, Margins, Bleed values with the mouse wheel - then these values increase by 0.1 - and not by 1 as in the entire software.

Only with the Shift key can you increase the value by 1, not by 10 - as in the entire software. And with the CTRL key the value increases by 0.01. Please correct this so that the values in the Setup Document increase by 1 with the mouse wheel, with the CTRL key by 0.1 and with the Shift keys by 10.

Thank you.

image.png.7fed71254e07c5301f4198183df222dd.png

 

 

 

 

Posted

If this is on Windows, this is not a surprise , probably this is a part or a continuation of bigger issue with incorrectly incrementing values app- wide in entry boxes using click n drag gesture, scroll wheel, [↑↓] keys with Shift and Ctrl modifiers — AF-2941. Which was found in 2.4.2 retail version. 

  • Staff
Posted

An issue raised in this thread ("Document Setup increments document size values incorrectly") has now been reported to the developers by the testing team (Ref: AF-2992). Thank you very much for reporting this issue to us.

Posted

Hi @Chris B,

Currently, it's governed by the number of decimal places set under 'Settings' and has always been this way...

Decimal Places | Margin Increment No Modifier Key | Margin Increment Shift Modifier Key

0 | 1 | 10
1 | 1 | 10
2 | 0.1 | 1
3 | 0.01 | 0.1
4 | 0.001 | 0.01
5 | 0.0001 | 0.001

Things go rouge when six decimal places are set, i.e.,

Without a Modifier Key, the increments are:
0.00001, 0.000019, 0.000029, 0.000031, 0.00004, 0.00005, 0.000059, 0.000069, 0.000071

With the Shift Modifier Key
0.000099, 0.000198, 0.0002, 0.000299, 0.000401, 0.0005, 0.000601, 0.0007. 0.000799

This differs from the Bleed increments which are 0.00001 and 0.0001 respectively...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • 2 weeks later...
Posted

In addition to this error, there is also an error when turning the mouse wheel in the Dimensions tab in the Document Setup window.

image.png.84f6a8e4c724b8f0e6a68d728b98a4ae.png

\

 

  • 3 months later...
Posted

 

This error when rotating the mouse wheel also occurs in the Radius and Miter fields in the Contour Tool and in the Corner tool in the Radius field. Beta 2.6 will be out soon, so it will not be fixed, so maybe version 2.7 in 2 years will have a chance to fix it?

image.png.11299ced33ea72e584583244d3016303.png

Posted
51 minutes ago, GRAFKOM said:

Beta 2.6 will be out soon, so it will not be fixed,

We don't yet know what bug fixes 2.6.0 beta will contain. And even if it's not fixed in 2.6.0, it could be fixed in 2.6.1, 2.6.2, etc. rather that waiting for 2.7.

 

-- 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.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5

  • 3 months later...
Posted

It seems Serif has no intention of fixing this annoying bug.

sn't there someone on the Canva team who can fix this?

Version 2.6 will be out in June and the bugs will continue to persist!

The problem affects the public version and the latest Beta version 2.6.0.2984. Should I create a new message in the Beta 2.6 Forums? Because the messages I am writing to are already in the Archive and no one from Serif reads them.

image.png.111655830fb4aeec185c6129f45be9cc.png

Posted

This thread has been given an official tag (AF-2992), which can be seen under the thread title.

When a thread has been given an official tag it means that Serif have logged it in their system to, at least, be considered for further work. Once an issue has been officially recognised and logged it doesn’t matter which section of the forums the thread is in as all logged issues are considered to be active issues with regard to them needing further investigation.

When something changes in regard to the situation as described in the thread, the Affinity Info Bot will make a posting in the thread explaining what has happened and what can be done about it (often simply upgrading to the latest version).

If the Affinity Info Bot has not created a post which says that the issue has been worked on, or fixed, you can assume that the situation remains as it was, from a user perspective. Serif don’t usually give us timescales for changes or fixes, or information about their plans for such, so it’s generally not worth your time asking for them.

If you want to know when a situation mentioned in an officially-tagged thread has changed, all you need to do is follow that thread and you will get a notification if/when this happens.

You can follow a thread by going to the top of any page of that thread and pressing the “Follow” button at the right of the thread header.

If an issue exists in the current commercial release of the software, regardless of whether it also exists in the beta, then it should be reported in a non-beta section of the forums because the only issues that should be reported in the beta sections of the forums are those which are extant only in the beta version.

  • 4 weeks later...
Posted

Just refreshing the topic, version 2.6 will be out soon.

And this annoying bug really interferes with everyday work.

I know Serif that you have 6 trillion bugs to fix, but find time to fix this bug at least in the next decade.

  • 2 months later...
Posted

Hello Serif, are you going to make a correction to this bug, version 2.6.2 is already released. Should I give up and stop reporting this bug? Let someone from Serif answer whether they even read these reports (and even more so in the archive) and I will never write about this topic again

  • 1 month later...
Posted

The production version 2.6.3 was released a moment ago. And this bug still hasn't been fixed. Is there anyone left at Serif who can fix this annoying bug? Maybe the guy from Vectorstyler could help you fix this annoying bug? It's been a year since this bug was reported, will 10 years be enough to fix it?

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.