davidbjames

Thank you Walt for your quick response. I would be grateful to anyone (including Affinity folks) who could provide more information on workflows that support sharing colors between documents. Am I missing something obvious?

I have a document palette of global colors. I would like to use this palette in different embedded AD documents and then update the colors in one place and have them update in the other embedded documents. Specific workflow: I have an AD file that I use as a template for creating iOS icons of various sizes. These icons are embedded AD documents. There are 4 variations – XL for iTunes store, L for high res devices, M for low res devices and S for search/notifications, and within each of those a few different sizes – Icon-60@3x, Icon-83.5@2x, etc. Each has the same general motif but slightly different design optimized for the size of the icon (e.g. smaller icons have less detail). To edit the documents, I double click on them which opens up the <Embedded> document. I need to be able to change colors in one and have those color changes reflected in the other embedded documents.

Just ran into this the other day. VERY frustrating. Considering the crazy math that must drive this app, the ability to scale dynamic corners proportionally seems easy to implement by comparison. PLEASE FIX!

Affinity staff, I would be grateful if you could take my last post as a bug report. This is still occurring for me. Thank you.

1. Create a background on a layer that extends across the screen 2. Create an object or text on the same layer (the size should be smaller than the background to see the problem) 3. Make the object into a mask for the layer so only the background shows for that area 4. Select the layer 5. (Note: the blue bounding box shows only the area of the mask, not the entire background) 6. Export > PNG > Area > Selection without background... Save. Expected result: PNG size to include only the selection/masked area. Actual result: PNG size includes the entire area of the background.

Thanks so much @dutchshader for the excellent video demonstration! (learned this today!) However getting back to my original question, should I report this as a bug? 1. Create a background on a layer that extends across the screen 2. Create an object or text on the same layer (the size should be smaller than the background to see the problem) 3. Make the object into a mask for the layer so only the background shows for that area 4. Select the layer 5. (note that blue bounding box shows only the area of the mask, not the entire background) 6. Export > PNG > Area > Selection without background... Save. Expected result: PNG size to include only the selection/masked area. Actual result: PNG size includes the entire area of the background.

Thank you. I love boolean operations! In any case, this is not a solution to my problem because I need to use masks (e.g. the background is much more complex than the rectangles I made in the example).

That's pretty cool @dutchshader How did you do that? Also is it possible to select the shape afterword to resize?

Here is a screenshot of the Export dialog, with the setting I want "Selection without background": https://cl.ly/50508bbd8932 I have attached a test document and exported document showing the problem. As you will note when opening the Designer document, the background of "FOO" are large rectangles that extend beyond the "FOO" mask. If you select the main layer you will note that the selection does not include the background, but only the masked area. However, if you export this (the Test Foo.png file) you will see that the resulting PNG includes the entire area, so requires trimming later. (I think all this was clear in my post, but now you have some examples to work with.) Test Foo.afdesign

Is it possible in Affinity Designer to export a selection (File > Export > PNG > Area: Selection without background) where there is masked content, with the resulting file being trimmed to only include the visible content. For example, I am creating a logo that has a background that extends well beyond the edges of the logo, where the logo shape reveals (via mask) the background I want visible. In fact, if I select the item in Designer the blue bounding box shows the rectangle of the visible content only. This is what I want to export. However, instead the export includes the entire area that the background occupies, so I then have to reopen the file in Preview to trim it down, which is obviously not very efficient. (btw, if I choose "Selection with Background" it then exports the entire file which I don't want. I just want the selection) Thank you, David

Excellent. Thank you.

Hi Sean, Thanks for the reply. I have attached the original. Can send the copy (it includes pre-release copyright) to you directly if you still need it. David iOS Icon Template.afdesign

I have a template file I use to create icons for iOS apps (see attached screenshot). It has 4 different icon variants embedded. Recently, I made a duplicate of the icon template (save as..) to create a new icon, and ever since then, whenever I open the duplicate or the original, Affinity pops up several warnings that "Linked Resource Changed / modified outside the application" (see attached screenshot). This happens in all versions of the file (originals, and copies) and regardless if I have changed anything -- i.e. every time I open these files I get all the warnings. NOTE: I do not change anything "outside the application", though the final exported PNGs are stored in the Xcode project. Affinity Designer 1.7.2 on Mac OS 10.14.6 Thanks, David

Ok. Next time it happens I'll try to reproduce it. Until then, I have the CMD-D workaround. Thanks for your time.

Per your suggestion, I opened the problem document and zoomed in and found the "marching ants" around the page, which are barely visible at any zoom level! This is very confusing and unintuitive. Also, I never use Pixel Persona. Sometimes Option-Drag stops duplicating for no apparent reason. You have pointed out the technical reason for it not to work, but not why this is happening in the first place, which really feels like a bug to me. The point is this: I do nothing special to cause Option-Drag to stop working, but occasionally it does stop working.