Pixel based document to be rounded up to the nearest whole number

[Bento]

Hi, 

 

i'm trying to figure out if, there's a way to work on a pixel based document wich would be rounded up to the nearest whole number.

 

I'll try to explain :

Let's say i'm working on a ui/ux webdesign, and my base value is obviously pixel. As i need my design to be as square as possible i really dont need all the decimals wich are more a pain to correct every time i create or move something. 

 

So is there a way to tell AD to get rid of decimals, and snap things to pixel perfect position ?

 

Hope to be clear enough.

 

Thanks !

[MEB]

Hi Bento,

Welcome to Affinity Forums :)

Go to the Snapping Manager (menu View ▸ Snapping Manager...) and enable Force Pixel Alignment ( you can also enable/disable it from the Persona toolbar on top - check the snapping section).

[Bento]

Go to the Snapping Manager (menu View ▸ Snapping Manager...) and enable Force Pixel Alignment ( you can also enable/disable it from the Persona toolbar on top - check the snapping section).

 

Hi MEB, 

 

first i'd like to say that you're always quick to answer, so thanks for that!

 

Second, it seems i'm already set to all these :

 

 

But i still have decimals. When creating a bloc or adding an image, or even when i use arrows to move an object px by px.

 

Am i the only one? Or maybe i'm missing something ?  :blink:

 

Thanks again !

[Bento]

I'll correct myself, arrows does move px by px but when using my mouse here is what appens : 

 

[MEB]

Hi Bento,

Force Pixel Alignment doesn't "fix" any existing object on your document. It only affects objects created after it has been enabled. Also note that other objects may also affect object creation/positioning. For example, if you try to align an object to the middle of another with an odd width, you may end up with an additional half-pixel. Move by whole pixels may also affect positioning if the original object width or heigh dimensions are not whole (integer) values.

 

I advise you to turn everything in the Snapping Manager off, except Force Pixel Alignment and then enable the rest of the features one by one as you need.

[Bento]

Right, i've tried a bunch of things, UX presets with only pixel alignments seems the best option for me.

 

But i'm still having an annoying issue :

 

 

Every time i move an object it had it a 0.2 pixel on the X axis...

 

And i can't even correct it definitly. It will be added again if i move it again.

 

EDIT it seems i've found what i was looking for :

 

Setup (if it could be usefull to anyone else) :

 

 

Result in action :

 

 

Thanks again MEB for your time !

 

Have a nice day !

[Chris_K]

Hi bento

 

Just for a bit further information, if you have Force Pixel Alignment on, but turn off move by whole pixel, any objects you have that are off slightly will automatically snap to whole pixels when moved. With move by whole pixel enabled, moving the objects literally adds 1 to the whole pixel value rather than snapping it to a full pixel first.

 

Cheers

[Bento]

 With move by whole pixel enabled, moving the objects literally adds 1 to the whole pixel value rather than snapping it to a full pixel first.

 

Wow good to know, it virtually adds it or it increase size/placement by one?

 

That's a tricky part. AD has a lot to offer but for the moment it's still a big learning curve for the every day routine. 

 

Are you guy's planning to do more Tutorials around the different setups and tools so that every use has its good habits? 

 

Anyway thanks again to the Serif team for your reactivity.

 

Cheers!

[VIPStephan]

This thread is revealing to me how people perceive functionality differently and how you can never please everyone. For me it was totally clear that “move by whole pixel” will change any value (even odd ones) by one, not force align them to whole pixels. For other people this is obviously a big question mark.

[diondiondion]

One thing that really threw me off in the beginning was that holding Alt to create a copy of a dragged object also disables pixel snapping, UNLESS you let go of the key after initiating the action. Took a bit of rewiring my muscle memory to get used to that.

 

Anyway, in my mind the "Force pixel alignment" checkbox could be stricter than it is now. It's safe to say that in UI projects, I don't want ANY sub-pixel values whatsoever, so it would be useful to be able to ignore those even when there are other mis-aligned items in the project (which may be unavoidable for example when importing & resizing images with a fixed aspect ratio). So maybe there could be a "strict" setting somewhere that actually does justice to the word "force" in the name of the option. ;)

 

For example, if you try to align an object to the middle of another with an odd width, you may end up with an additional half-pixel.

 

 

That's actually another good example: I think "Force pixel alignment" should also apply to objects being distributed or aligned to objects with odd widths - sharp strokes and container edges are more important to me than mathematical accuracy. (And it's not like anyone would notice - web browsers for example center-align objects with pixel snapping, so they're not 100% accurate - but at least the borders are never blurry.)

[ralphonz]

One thing that really threw me off in the beginning was that holding Alt to create a copy of a dragged object also disables pixel snapping, UNLESS you let go of the key after initiating the action. Took a bit of rewiring my muscle memory to get used to that.

 

Anyway, in my mind the "Force pixel alignment" checkbox could be stricter than it is now. It's safe to say that in UI projects, I don't want ANY sub-pixel values whatsoever, so it would be useful to be able to ignore those even when there are other mis-aligned items in the project (which may be unavoidable for example when importing & resizing images with a fixed aspect ratio). So maybe there could be a "strict" setting somewhere that actually does justice to the word "force" in the name of the option. ;)

 

 

That's actually another good example: I think "Force pixel alignment" should also apply to objects being distributed or aligned to objects with odd widths - sharp strokes and container edges are more important to me than mathematical accuracy. (And it's not like anyone would notice - web browsers for example center-align objects with pixel snapping, so they're not 100% accurate - but at least the borders are never blurry.)

I would tend to agree with this.  In my UI or web design projects I don't want ANY sub-pixel values either, they just make a mess of everything. It'd be really handy to just disable them altogether and make the force-pixel alignment much more strict - in fact make it into an evil nasty draconian dictator of a function so you can annihilate those sub-pixel values when you want to!

[Bento]

We are quite a few asking for that kind of option.

But for now never had a positive answer from the team that it would be done one day. Sad...

[Mithferion]

We are quite a few asking for that kind of option.

But for now never had a positive answer from the team that it would be done one day. Sad...

 

Hi, I don't know if this will work for you. Set 0 in Decimal Places for Units Types for Pixels (see attachment).

 

Al least it works form me most of the time, but not exactly the Always Pixel Perfect feature.

 

Best regards!