Jump to content

Recommended Posts

Posted (edited)

Is the Margin setting feature ONLY for Publisher, or valid for Designer & Photo as well ?
If so, I think I stumbled upon an issue with setting them. If only valid for Publisher, please disregard this post.
Aff.Photo & AffDes
Page size = A4, Landscape & Portrait.
Printer margins : none (print to edge of paper)
-----
As tested in Photo, AffDes 170.14 the same but different method for setting margins.
File New>Document>Margins>Set margins at 10mm, sequence T,L,R,B>OK.
Only the T,L,R margins show. Also when viewed/set through the GuidesManager.
When I choose "Retrieve from Printer" I end up with the margins set at 31,8/25,4/25,4/31,8 mm respectively.
The printer's margins themselves are set to NONE, though.
When trying to rectify the settings by re-typing in the bottom margin, I end up with the T,L & R margin gone.

Please have a look at the attached MOV & scrnshots.Thank you.

Screenshot 2019-06-02 at 17.00.34.png

Screenshot 2019-06-02 at 17.01.12.png

Edited by catlover
inserted images too large
Posted

I am seeing none of that behaviour here on Mac.

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

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

Posted

I have tested this again, it looks like the problem lies with the SEQUENCE of typing-in the margins :
Each time the very last margin typed in won't show, no matter which one is the last, it won't show.

Very strange....;)

Posted

Hi, FDE101 :
Thanks for the tip, followed your suggestion right away.
And what do you know : it works OK when tabbing through the fields & typing in the value, all margins show.
It does NOT work when using a combination of tabbing and moving to the next field "manually-click & type"

The margin of the field to which I moved the cursor manually & typed in the value doesn't  show.
I wonder what could cause that ?

Posted
58 minutes ago, catlover said:

I wonder what could cause that ?

A bug in the code, most likely.  Something for Serif to look into, but that info might be helpful to them.

×
×
  • 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.