Export problem

[Kirill_M]

Hello!
I have been using AD for many years now and I am very pleased!
Why during export an additional pixel? 
For example: a square of 110x110
Export: 111x110 

This happens very often (

Version AD: 1.8.3, El Capitan 10.11.6

 

[walt.farrell]

Welcome to the Serif Affinity forums.

Look at the X coordinate of your object. You'll see that it is not an integer, and that is what gives you the extra pixel.

[Kirill_M]

Yes, thanks, I see it!
This is very inconvenient in working with projects. (Watch for every pixel)
Can I customize the program so that there are only integers?

[walt.farrell]

What you can do is enable Snapping, and within the Snapping options, enable Force Pixel Alignment. You may (or may not) want to also enable Move by Whole Pixels. Opinions seem divided over that.

The important thing is that you do this at the very beginning of a project, and that you avoid using the Opt key (Mac) or Alt key (Windows) to  override the snapping when you move or duplicate objects.

[lepr]

12 minutes ago, walt.farrell said:

You may (or may not) want to also enable Move by Whole Pixels. Opinions seem divided over that.

It's not really a matter of opinion. When Force Pixel Alignment is enabled, Move By Whole Pixels must be enabled if the user wants to preserve an offset from the document pixel grid when moving an already offset object.

[walt.farrell]

13 minutes ago, anon2 said:

It's not really a matter of opinion. When Force Pixel Alignment is enabled, Move By Whole Pixels must be enabled if the user wants to preserve an offset from the document pixel grid when moving an already offset object.

Yes, but for most problem reports the users are wanting objects to stay pixel aligned, and in that situation you would want the "Move by Whole Pixels" option off, generally.

Where opinion comes in, is that some users seem adamant that the option should be on, and others that it should be off.

[lepr]

4 hours ago, walt.farrell said:

Yes, but for most problem reports the users are wanting objects to stay pixel aligned, and in that situation you would want the "Move by Whole Pixels" option off, generally.

Where opinion comes in, is that some users seem adamant that the option should be on, and others that it should be off. [bold is my emphasis]

When Force Pixel Alignment is enabled and an object is already aligned to the document pixel grid, the status of Move By Whole Pixels becomes irrelevant when moving the object - the object will stay aligned to the document pixel grid regardless of the status of the switch or people's opinions.

[Kirill_M]

Thank you so much.

At the moment, enable Snapping solves my problem.

[R C-R]

On 5/30/2020 at 6:55 AM, walt.farrell said:

Where opinion comes in, is that some users seem adamant that the option should be on, and others that it should be off.

Personally, I would prefer that it was off by default (IOW, that clicking Force Pixel Alignment did not also automatically enable Move by Whole Pixels).

That said, IIRC in some earlier versions of AD this was not a "sticky" setting but now it seems to be -- once I enable Force Pixel Alignment & then disable Move by Whole Pixels, toggling on & off Force Pixel Alignment does not also auto-enable Move by Whole Pixels.

[bures]

See 

 

[walt.farrell]

2 hours ago, bures said:

See 

 

Yes, that's the issue we're talking about. You need to make sure your artboards are on integer X/Y pixel coordinates, in addition to having integer pixel dimensions.