Jump to content
Aleksandar Kovač

Extra-small change -> Extra-large problem

Recommended Posts

(Dear moderator, please move this to Publisher bugs forum... and sorry for posting here by mistake)

There is, I believe, an issue regarding linked multi-artboard Designer documents in Publisher. Imagine this situation:

Our designer is using Affinity Designer to create graphics for our printed presentation. In one Designer file she creates one artboard per each graphic and saves that file to a shared folder. 30 neatly named artboards in one file. I am laying out the printed presentation in Publisher. Frames are laid out on spreads and Designer file above is linked. I am using her artboard names to chose which artboard goes in which frame in my Publisher document. Everything is nice and clear. Hoity-toity.

Now, I did not know that just now our designer moved one little tiny artboard in Affinity Designer's layers palette. By mistake or on purpose, the artboard is not on the top of the palette anymore. It is now at the bottom. No artboard names were touched, no content changed. She saved the file. Went out. On my side, Publisher's assistant warns me politely that linked resource changed... oh and how!... none of the frames laid out so far are right anymore! I can see that each frame in Publisher now contains some other artboard from the linked file and not the artboard I wanted... Uncomfortable. 30 frames to edit?...I realized that layer order, rather than artboard name or some universal identifier is what determines what will be displayed when Designer file is linked.

...

My gut feeling is telling me that linking artboards using some UID would be a more rational approach here. That way, artboard's position in layers palette would not matter and even artboard name could change and not totally mess up Publisher document. Or not?

I understand that artboard is a container. With that in mind, a user probably wants a certain container in a certain spot in her/his Publisher document and not e.g. 'container 3rd from the top in Layers palette'... or maybe my approach to this is wrong? Would not be the first time... :)


Alex

iMac (27-inch, Late 2009), macOS High Sierra, ATI Radeon HD 4850

Share this post


Link to post
Share on other sites

Just a comment: this seems like a Publisher issue, involving Designer files. But you've posted in the Photo Bugs forum.

Perhaps a moderator will move it :)


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.7.3.475 Beta

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.