Wosven

We've got the same error message, when the app encounter a not-yet-finished-saved file. This would also trigger errors with other apps, for example on a server, when Pitstop try to take a PDF before it's finished copying, etc. I'm not sure there's a solution for this problem.

It was already mentioned here:

Hi @ahnay , Like this?

Hi @Greybeard53, If you could provide samples to search where is the problem, it would be useful.

If not installed, but read and accessibles when the document is open, it would be better. Avoiding cluttering the asset or swatches panels. And if possible, being able to add swatches or assets to the items, with an option to automatically update them (sort of like the slices), could be a nice addition. In fact,it would be like the package folder was like a folder, once exported.

Or such added fee for redoing the work again and again that the main editor would manage to get the last draft of those texts before the first proofreading for corrections*... if not in this edition, in the next book Best practice would be to have the proofreading done first. In your case, there'll be many proofreading for the texts, and many reflowing of the texts... a really bad situation with wasted time.

Using the tab stop as said by @MikeTO seems more logical, since "0 dph, 3 dph, 4 dph..." isn't an unit (I suppose in other lists it can be "0 dph, 1 dph, 5 dph...". Ordered lists work the same way since they also use a tab, but the ordered unit will be the same, increase the same on each list, an what you need is different.

You're wrong, they go well and the result is nice: https://www.clarisvirot.com/en/home/2620-gold-turtle-python-chocolate-belt.html

Hi @William Overington, You can play with the Turtle here: https://turtlegraphics.fun/overview.html Have complexe examples: https://turtlegraphics.fun/examples.html And try to do your owns, and save them as PNG (sadly no SVG): Demo You can have fun here also: https://codepen.io/adrianparr/pen/MYyWdq If you have LibreOffice, you can also play with it (from https://en.wikipedia.org/wiki/LibreLogo): And some tutorial: http://www.stuestoel.no/office/logo/en/logo-opna.php

I don't want generic paths for all the files, but paths by document, saved inside each document. And possibly last name used for export, since nomenclature of working files can be different from the name use for a PDF send to the client. But keeping the last name used, as in "Blabla_v2" can be usefull, to use "Blabla_v3" at the next export. It's possible to do it in the export persona, but not in APub, and it's annoying, since you need to check or not overwrite a file if you try to guess. This means: for saving an new Afinity file for the first time after creation (new document panel): path to the last used folder for saving an new Afinity file for the first time after opening it in the app (images, PDF...): path of the original file for "saving as" a file for the first time: path of the original file for "saving as" a file for the next time: last path used for this action for this file for exporting a file for the first time: path of the original file for exporting a file for the next time: last path used for this action for this file for importing a file for the first time: path of the original file for importing a file for the next time: last path used for this action for this file Since we tend to organize work in folders, it would be logical to use the original file's path as default, or the one set after a first use (this one saved inside the document). We could also have 2-3 options in the preferences, to set (or not) default paths for all imports, exports and packages. And if the path is unavailable for an action when the file is open on another computer, it would use the default path if the one saved in the file isn't available, and only overwrite it if the action is done. Different users can open and work on the file, but not all of them will export/import (some will only work on text, some will just drop images from Explorer/Finder, etc.), so the paths set by the main user stay in the file.

Ça a toujours été comme ça. Peut-être que tu utilisais : Document > Aplatir, où dans ce cas, effectivement, il ne reste plus qu'un seul calque.

In some instances, pasting with it enabled add bugs... So remember it, it can be useful

In the general preferences, try using "Copy as SVG".

On further inspection, nothing happens with your adjustement in the AP file (same red with or without), and in the end we've got real text in the different PDF, 1.7 or PDF/X. For the TIFF file, the text is rasterised, but there's no difference between the backgroung blue, but around the text, like a darker stroke, in the PDF 1.7 version. To sumarise: transparency in PDF/X is correctly flattened and the details and background are correct. It's completely different with other PDF versions.

There's certainly bugs... that's why I'd rather export using PDF X-1a to avoid such problems. I used a recolor adjustement, to be sure, if it was modifying the backround, to be able to see some evidence... PDF for print using PDF 1.7: Background Color Inconsistency ProblemForPrint.pdf PDF/X: Background Color Inconsistency Problem_PDFX.pdf Background Color Inconsistency Problem_PDFX.pdf Background Color Inconsistency ProblemForPrint.pdf

It can be tricky, if you modify the size of the image, and it's automatically updated. The result can be different, or badly cropped in the frame... only displaying details. That's why I usually tend to check each update of content…

Or you can have a yellow /!\ on the top of your frame, you just need to click it to refresh the link.

But you can draw first the image's frames, and drop the images inside from the Explorer/Finder. There's no visual indicator on the frame to specify it was modified, and it would be useful, but instead you can click on the red light at the bottom, it'll display the Preflight panel, and you'll be able to correct it simply clicking on a button.

Check your PDF, but the text will be rasteried... perhaps not what you want in the end.

One is simply an image, and the other one is a picture frame, with more options since you can modify the frame, auto-resize the image inside, etc.

1. Create the needed number of square, tag them with a same colour and a stroke, space them as needed and put them below everything 2. Duplicate the document, and keep only the part with the icons and squares, delete all the other artboards and content, ungroup the objects and get them out of any Layer, before deleting the Layer. 3. And that's where the lack of "redo" or other iteration through selected objects is really missing in the apps: use the Artboard tool,set it on "selection", and select one by one each square, and click on the button "Add an artboard" (don't use the "convert to artboard" option in the menu, since it won't add the objects above inside the artboard). 4.Select all the squares (similar tag colour), and set the stroke to 0 and no colour (or delete them) 5. Use the export persona Being able to duplicate some slices would have been another good method if it exists... since we can select different ones and align them (but not resize them once selected ).

There's no problem with X-1a, it's simply a setting that will rasterise only objects with transparency (opacity different than 100%), but it won't modify or rasterise text or any other object on the blank canvas. My first export CMYK is done with such preset. When I export a ±1050 pages"black" book from ID with such PDF/X-1a:2001 setting, the file is 12Mo. 20 Mo if I keep the 6 pages with illustrations. If I import the IDML in APub, sadly, the text stop flowing after 150 pages, variables and footnotes are lost. Once exported with the images, it's a 22Mo PDF. Perhaps Affinity need to check your file, since there's certainly a bug.

I don't have any problem either, file is under 3Mo, less than a minute for export. I simply replace part of the font (this need adjustemznts, but it's for another thread), and replaced the logo. @AdamCPDid you tried without logo? sampleAdam3_CMYK.pdf sampleAdam3_Grey.pdf sampleAdam3_forPrint.pdf

Why not using a second Paragraph style for those notes, and restart the paragraph numbering? Something like this: OLexample.afpub

@AdamCP How many pages in your document and which preset when exporting? Can you post a dummy file with Lorem Ipsum or similar? Your problem look strange. Does a "saving as" of your files make them lighter and able to export smaller PDF?