Jump to content

0.1 px difference while snapping to spread?


Recommended Posts

Hi everyone,

I have an annoying problem while using affinity designer and publisher. I use them to arrange my figures a lot, just to make them aligned. I think the fastest way to do this is snapping. However, when I enable snapping to spread, even with force whole pixel movement on, I got this strange problem: sometimes when it seems to be snapped, there is actually a 0.1 pixel difference. See below screen shot and the numbers in red rectangle. I tried to snap the figure to the corner of the spread, and both 0 and 0.1 px can make it looks like snapped. I have to be very careful to make it snap to 0 px.

I know I can type a number. But it is not as convenient as snapping. I am wondering if this is meant to be? And is it possible to correct it somehow?

Thanks!

 

image.png.6eb3bc71213abf89cd2eccba95d48b29.png

 

Link to comment
Share on other sites

3 hours ago, rocthered said:

However, when I enable snapping, even with force whole pixel movement on

Never use „move by whole pixel“ (there are rare exceptions- this case is none). It is a recipe for such issues.

when using snapping, either snap to whole pixel positions, or to grid, or to other objects. You need to choose one, don’t activate multiple at once.

this advice is for beginners. Snapping is extremely powerful, unfortunately heavily loaded with so much options that it is hard to master. Try to activate only the smallest possible set, save as preset, and choose one preset specific for every use case.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.

 

Link to comment
Share on other sites

2 hours ago, NotMyFault said:

Never use „move by whole pixel“ (there are rare exceptions- this case is none). It is a recipe for such issues.

when using snapping, either snap to whole pixel positions, or to grid, or to other objects. You need to choose one, don’t activate multiple at once.

this advice is for beginners. Snapping is extremely powerful, unfortunately heavily loaded with so much options that it is hard to master. Try to activate only the smallest possible set, save as preset, and choose one preset specific for every use case.

Hi @NotMyFault,

Thanks for the reply!

However it still happens, with only one snap option is on: snap to spreads. Did I understand you correctly?

image.png.43f020ceaa0d36b7518f4d71520f3658.png

image.png.0fee33a5d5236a0ee518a74de83b1e35.png

Link to comment
Share on other sites

2 hours ago, thomaso said:

Had you moved the ruler's origin? Just in case, double click its intersection (unit) to reset to 0/0.

Hi @thomaso,

The spread origin is 0,0, if it is what you meant. Actually, currently -0.1, and 0 px both look like snapped, so not very likely related to ruler..

image.png.5e1e3b897f907cea386b15584ddb02b6.png

 

 

Link to comment
Share on other sites

10 hours ago, rocthered said:

I got this strange problem: sometimes when it seems to be snapped, there is actually a 0.1 pixel difference.

I also know such inaccuracies. The smaller an object is on the drawing surface, the more likely it is to snap into place "crookedly". A larger zoom level can then help. Or manual/numerical alignment.

Thanks to DeepL.

Link to comment
Share on other sites

For Pixel perfect design need Force pixel alignment On, and Move by whole pixels Off. 

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.5.2636 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

19 minutes ago, rocthered said:

But to be clear, the problem is in snapping to spread, not to object.

Then it is an issue with either the ruler origin or "just" a ruler inaccuracy.
With other words: it does not snap to a wrong position but rather "just" reports wrong position values.

Test:
1. Untick the snapping force and full pixel options.
2. Create somewhere on the page two rectangles: numerically & without decimals.
3. Let one drag-snap to the other (side by side).
4. Select both and let one snap at the spread origin.
5. Result: Does each of them report the 0.1 px decimal?

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
Share on other sites

2 hours ago, thomaso said:

Then it is an issue with either the ruler origin or "just" a ruler inaccuracy.
With other words: it does not snap to a wrong position but rather "just" reports wrong position values.

Test:
1. Untick the snapping force and full pixel options.
2. Create somewhere on the page two rectangles: numerically & without decimals.
3. Let one drag-snap to the other (side by side).
4. Select both and let one snap at the spread origin.
5. Result: Does each of them report the 0.1 px decimal?

I believe it is not just wrong reported position values. I tried to duplicate a rectangle, snap one to the spread corner with 0, and another with -0.1. When I zoom, I can see the difference like below screen snot. I think the problem is both 0 and -0.1 can snap:

 

I will try what you suggested. Thanks!

image.png.5bb4c9cd57c5167cdbcfefb5ed9ac67f.png

image.png.77cbc9494937c8a882b678b843cfb87a.png

 

Link to comment
Share on other sites

2 hours ago, thomaso said:

Then it is an issue with either the ruler origin or "just" a ruler inaccuracy.
With other words: it does not snap to a wrong position but rather "just" reports wrong position values.

Test:
1. Untick the snapping force and full pixel options.
2. Create somewhere on the page two rectangles: numerically & without decimals.
3. Let one drag-snap to the other (side by side).
4. Select both and let one snap at the spread origin.
5. Result: Does each of them report the 0.1 px decimal?

I tried as you suggested. When I select both, I can either snap them to 0 or 0.1. Both of them will show the similar number as I snapped.

Link to comment
Share on other sites

19 minutes ago, rocthered said:

When I select both, I can either snap them to 0 or 0.1.

Indeed only when you select both?
What x/y values does the Transform panel report if you select only that object which is not placed at the spread edge?
Just in case: What are your bleed settings?

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
Share on other sites

1 minute ago, thomaso said:

Indeed only when you select both?
What x/y values does the Transform panel report if you select only that object which is not placed at the spread edge?
Just in case: What are your bleed settings?

Uh that's it! Turned out my bleed was set as 0.1 for all four positions. Not sure why it's like that. I don't remember I ever set it that way...

Thanks a lot! After changing them to 0 the problem seems to be fixed! 

 

 

 

 

 

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.