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

Dragging image into document positions it at fractional X/Y coordinates despite force pixel alignment and snapping


Recommended Posts

If I have an image open, with force pixel alignment and snapping enabled, and I drag another image onto it...that second image is more often than not positioned with a fractional (not pixel aligned) X/Y coordinate.

video demonstration - note how the image I drag in has a fractional X value

Affinity Photo 1.10.5.1342 / Windows 

 

similar/related to this other topic (which is still a problem)

 

Link to comment
Share on other sites

Do you have ‘Move by whole pixels’ disabled? Do the source and destination documents have the same document DPI?

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

Link to comment
Share on other sites

As Alfred asked turn off the middle one.

983221132_ScreenShot2022-07-10at7_11_11AM.png.a0312b2e2854dea0d57732a646d3e80f.png

Mac Pro (Late 2013) Mac OS 12.7.2 
Affinity Designer 2.3.1 | Affinity Photo 2.3.1 | Affinity Publisher 2.3.1 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

I see the same behavior for drag/drop from an external source such as File Explorer. The initial drop isn't pixel-aligned. Any movement using the Move Tool after that aligns it, though as long as Move by Whole Pixels is off. (One generally should have that option off, in my opinion, except for special occasions.)

One additional oddity, though: After dropping, and having it end up not aligned to the pixel grid, if I move it using the arrow keys, it does not snap to the grid. I must move it using the mouse.

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

Link to comment
Share on other sites

I wonder what else is turned on in for Snapping. When I want pixel aligned work I turn off anything related to Mid points and Margins and guides as these can easily be at fractional locations. Then there is snapping to other objects, they may not be at whole pixel locations. 

In essence if pixel alignment is important then enable Force Pixel Alignment and turn everything else off.

A note on Placing a file, the file may be 1200 x 900 pixels in size and when you place it by dragging to size you have it at 481 pixels wide and you will then have a fractional pixel difference in height.

Mac Pro (Late 2013) Mac OS 12.7.2 
Affinity Designer 2.3.1 | Affinity Photo 2.3.1 | Affinity Publisher 2.3.1 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

Quote

I wonder what else is turned on in for Snapping

See screenshot above. I've turned off all midpoint etc stuff. Only snapping to grid (which is set to 8x8 with 8 subdivisions, for arcade/console game tile work), snap to guides, visible objects and their bounding boxes.

Quote

if pixel alignment is important then enable Force Pixel Alignment and turn everything else off

makes no difference in this scenario, I tried it. still results in fractional coordinates (same in the copy/paste scenario of the other thread).

 

Link to comment
Share on other sites

52 minutes ago, patrick_h_lauke said:

See screenshot above

You still have Move by Whole Pixels checked. And if your grid is set to something other than whole pixels then this won't work. Not to mention that Only Snap to Visible Objects might result in no snapping if you are not starting near a visible object.

Play around with having only Force Pixel alignment set. All else off.

 

Mac Pro (Late 2013) Mac OS 12.7.2 
Affinity Designer 2.3.1 | Affinity Photo 2.3.1 | Affinity Publisher 2.3.1 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

as said, my grid is set to be pixel accurate as well (8x8 with 8 subdivisions)

and no, even *just* having "Force pixel alignment" on and nothing else, dragging an image over still results in fractional coordinates (but yes, after that moving them snaps them back to the pixel grid, but i'd really expect it to do that already without having to nudge it first)

 

image.png.69115e89196199b5f7ac1a0f63087677.png

Link to comment
Share on other sites

Placing an file is not related to move tool. You can place a file unrelated to any tool. The snapping settings are unfortunately related to specific tools, not global. So i agree that the observed behavior is unfortunate and should be changed asap, but unsure if you can argue it is a bug.

Mac mini M1 A2348

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.

 

Link to comment
Share on other sites

however, the snapping etc settings aren't shown as being just settings for the move tool. they appear in the top toolbar (not the context toolbar for the specific tool that's currently used). saying they're just specific to the move tool seems a bit odd...they're more along the lines of application-wide properties/settings

Link to comment
Share on other sites

Just now, patrick_h_lauke said:

however, the snapping etc settings aren't shown as being just settings for the move tool. they appear in the top toolbar (not the context toolbar for the specific tool that's currently used). saying they're just specific to the move tool seems a bit odd...they're more along the lines of application-wide properties/settings

Yes, it is far from clear to which operations snapping gets considered or not.

  • Move tool, crop tool, creating vector shapes get impacted by snapping
  • Pen and node tool has special snapping options for nodes and handles
  • unsure about selection tools

Mac mini M1 A2348

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.

 

Link to comment
Share on other sites

1 hour ago, patrick_h_lauke said:

from the help/documentation

 

Good find. It does not explicitly mention placing of layers, so it is up to Affinity to clarify.

Mac mini M1 A2348

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.

 

Link to comment
Share on other sites

  • Staff

Hi @patrick_h_lauke,

Thanks for your report!

I can confirm that when using File > Place, these snapping options are respected - however when dragging and dropping the file from an external source (such as Explorer/Finder) I'm able to replicate the issue reported here.

I believe that these should be respected when dragging and dropping, so I'm logging this as a bug with our developers now.

19 hours ago, walt.farrell said:

One additional oddity, though: After dropping, and having it end up not aligned to the pixel grid, if I move it using the arrow keys, it does not snap to the grid.

I can confirm this is expected behaviour, even with Force Pixel Alignment enabled. Nudging using the arrow keys will always move the layer by 1px (or by your specific nudge amount in Preferences), regardless of current part pixel location.

I hope this helps :)

Link to comment
Share on other sites

  • Staff

No problem at all!

I'm not able to replicate the behaviour your seeing in this thread provided, with Force Pixel Alignment and Move By Whole Pixels enabled, both selections and full layers are pasted in the same X&Y locations, respecting Force Pixel Alignment.

Please see this below using a document at 45px x 34px & 150px x 150px, both at 300DPI.

As can be seen, a Quick Shape (rectangle) copied from X0,Y0 in the smaller document is pasted at x0,Y0 in the larger document, a pixel layer or pixel selection is also pasted at the same X&Y locations, with the correct full pixel value for H&W.

Do the DPI's between your 2 documents match?

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.