StanA

@IAmMatt: I guess we should all be grateful we don't have to use a Linotype machine then... Although you can do that, write everything in Word, remove all Mendeley/Zotero field formating and copy paste to Affinity. But then what happens if you have to remove or add a single citation, or move position? You have to do it all again in Word (because you have to update all the fields that come after your change!), remove all text in Publisher and replace with the new text from word again. This is a) a lot of work and b) prone to errors.

Hi @stokerg, thanks for the reply. I'm not sure whether I understand it. What do you meen by "set a place PDF which will be using Passthrough as default"? You mean just place any linked PDF? The preflight warnings is not what's bothering me, rather I don't want the PDFs to be rasterized.

Great, thanks for the reply.

I have update to 1.9.0 but the problem was there with the latest version of 1.8 as well. I'm not sure whether it's a wrong setting. All the linked PDFs in all publisher files that I cropped with the vector crop tool are now scaled to fit the entire page after updating the scource file, this is horrible! Have to redo all scaling and cropping each tie after updating a linked PDF externally. Edit: found a workaround by putting each PDF to be cropped into it's own group and applying the vector crop to this group. Shouldn't it work with the crop applied to the linked PDF itself though?

I have a file with a lot of linked PDFs, the new "PDF passthrough" feature is killing me! It is set by default for all the single PDFs!!! What's worse, each time after updating a link (externally modifying a pdf) the setting is set to passthrough again!!! Whats even worse, preflight is now full of errors like: "Placed PDF Version (PDF-1.5) is not compatible with the PDF export version. The PDF will be rasterised on export."!!! How can I disable it for the entire document? Or set "interpret" as default?

I have downloaded 1.9.0 from the Mac App store. Now the updates are to the right page of PDF. However, the previous image was cropped by me using the vector crop tool, but after the update publisher makes the whole page of the pdf (as apposed of just the region I cropped into) fit into the crop. What's the problem there? Actually all the linked PDFs (even those with only one page) that I cropped with the vector crop tool are now scaled to fit the entire page after updating the scource file, this is horrible! Is it some setting or is this a bug. I'll start a new post on that. The original problem of this post about the pdf page has been solved in 1.9

Does anyone else have this problem? Is it fixed in the coming version 1.9?

The title basically says it. I am using the most current publisher App Store version (1.8.6). If I place a linked images to pages from a multipage PDF, then change the PDF (externally), open Resource manager, click on the pdf and Update the links, then for some reason more often than not the linked images change to the first page of the pdf, also the size for some reason changes.

Thanks Old Bruce. After some trial and errors it seems that all objects have to be selected in order for the node tool to be able to select some of their nodes. Is there maybe some setting one could activate to achieve a different behavior? I'd like to be able to simply click and drag around the nodes that I want to select with the node tool irrespective of whether the objects are selected or not. Same as it does in Illustrator.

I had a problem going into a similar direction when trying to change the language for text objects within a group. If I chose a group (with text objects inside it) and change the language in the paragraph panel that change only applies to the group itself, not the text objects inside of it. I'm not sure why it would make sense to have an attribute such as language to be assigned to a group, but not the objects inside of it, effectively not changing the property for any of the text objects (they still have the previous language selected). It would be great to have an option to have changes applied to a group (such as text size) propagate to all of it's elements. Selecting each element from the layers panel I find is not a good solution for complicated graphs, such as flow diagrams, etc. It forces you to give a name to each element so you can identify them, could be very cumbersome.

Not sure if this is a newbie question, but is there a way to select and e.g. move nodes from several objects (which may or may not be in different groups) or can the node tool only simultaneously select nodes from a single object?

In Adobe Illustrator one can select multiple groups of objects (text, shapes and other) and then simultaneously change the font size for all text objects within the selection. How can I do that in Affinity Designer/Publisher? When I select groups of objects that contain text and non-text under Menu (Text->Size) the options are greyed out.

I would also very much appreciate such a feature. I think it could be solved by citation companies (such as Mendeley) once Affinity introduces Plugin Architecture. So here also +1 for a need of Plugins in Affinity.

I fully agree, Camera-RAW like sidecar files would be an immediate huge feature! especially if combined with media browser (which for some reason appears to have been removed in the current version 1.7)

This is the same feature as was discussed here: https://forum.affinity.serif.com/index.php?/topic/100793-how-to-show-histogram-only-for-masked-adjustment-layer/&tab=comments#comment-539760 I think many serious photographers are using local masks for the levels adjustment layers in photoshop and take advantage that the histogram in the levels adjustment only shows the values for the selected region. E.g. it was one of the main tools for Ben Long in the Lynda.com course on Photography printing: https://www.lynda.com/Photoshop-tutorials/Inkjet-Printing-Photographers/103678-2.html. Would be great to have it in affinity photo. I actually couldn‘t find any other software for macOS that would implement it, which seems strange, shouldn‘t be too difficult... OpenCV does it, so shouldn‘t be an Adobe patented feature.