joe_l

I know, my example was just to clarify the inconvenient way of "creating" several asterisks. In technical documentations I use them frequently, so I am hoping for a more elegant way.

Make the drawing smaller or make the page temporarily bigger or copy the drawing to a new bigger page. The drawing is partially hidden by "potential" pages above or below the page, which is "by design" in APu.

This is only reproducable with a certain document. In new documents it works as it should be. In my non working document the text came from a PDF and I applied on all text the same formatting. 🤷‍♂️ shrinking-text.mp4

Thx for your efforts, but don't waste too much time on this. The bug seems to be on my side.

I know, that I can use asterisks for footnotes, but there is IMO room for improvement. To get ** I have to restart numbering at 7, for *** restart numbering at 13, for **** restart numbering at 19 etc. pp. It would be nice, if the available special chars could be selectable or be separated.

Perhaps it is my inability to explain the "problem" properly as I think you are doing something different. So I try again to explain my workflow. 0. Am I correct, that there is no way yet to hide or show layers of a linked .afphoto document as I can do it with .afdesign documents (see screenshot)? 1. Since toggling layers does not work (for me) with .afphoto, I edited the .afphoto file in AD, added there REAL layers and moved the elements into those layers. Then switched back to AP to do further editing and saving. 2. Placing this file allowed me to toggle the layer visibility (like in the screenshot). 3. I edited the same .afphoto as explained in 1., added a layer, the file was automatically updated in APu, but the new layer did not appear in the layer dropdown. If my workflow is all wrong I learned, that I simply have to replace the .afphoto to make the additional layer appear. So all is good on my side. This was just an observation.

When I understand you correctly, you toggled the visibility of the layers in AP? I am talking about toggling the visibility of the layers in APu!

Hard to tell from just a screenshot. Normally works without an issue. Did you use FX, adjustments or non-vector brushes? Could you share your Affinity document here for further inspection?

Done!

This link is not valid or valid anymore, so you have to give me another one please.

Export to PDF and print from a PDF reader as a workaround.

Various, to be precise. 1) How many pages? If several pages, split the document into half (and the half into half and the half of the half into half etc. pp), to see where the problem is. 2) Replace all fonts with others. Maybe font related. 3) Check the images. Some image applications allow e.g. CMYK images to have a RGB ICC profile. 4) I am not sure if PDFLib logging is also working for V2. Worth a try: 5) If nothing helps. Make a package, zip and upload the package to the forum. If your project contains private data, ask a moderator for assistance and an upload link.

X3 was already attached to my last post. What do you mean by lost backgroud?

Also no problems here on Windows 10 Enterprise. Attached X4- / X3-PDF and the "fixed" document. couveclat01_test-fix.afpub couveclat01_x3.pdf couveclat01_x4.pdf

The document exports fine as PDF-X4 or PDF-X3. Last thing: You uploaded the images here to the forum, but the forum software alters the images, so they are not in their original state anymore. As a final test, please zip the two images and upload them here. What you can do already, is to replace the used fonts with other fonts, just to make sure your problem is not font related.

Thanks. Opens fine ... but still a problem. Images and fonts are missing. So it would be still guess work, because a X3 export works okay from this "incomplete" document. Maybe you can save this project as a package and upload again?

Yes, I can do this. To add something strange. Placing the PDF in V1 looks fine ... until I close and reopen it. The text is shown wrong and minified. So I really suspect PDFSharp is to blame here, but the differences between V1 and V2 are interesting anyway.

To make it clear: I like the Affinities. A lot. And I highly appreciate the work Serif puts into it. But V2 is plagued by a massive amount of bugs, which reminds me of the (German?) term "Banana software, which ripes at the customer". Has Serif to rethink QA? I have this feeling over some bugs, which should not be part of a retail version. So for now, I am using V2 for unimportant projects, learning to master the new software / features and bug hunting (not MY task so to speak). Serif did not met the hype about V2, but I have high hopes, that they will fix the bugs and deliver a stable V2 I can enjoy for daily work. I am sorry for the mild rant here from a faithful customer. 🙄

Not at all. But I cannot open it in V2 as I get the message, that it contains features from a newer version. Is V3 released and noone told me? 🤔

Maybe you should check your images. E.g. Anne Minot looks like it is CMYK with a RGB ICC profile, which is wrong.

Z. B. eine blaue Linie anklicken, dann Menü > Auswählen > Gleiches auswählen > Konturfarbe und dann die Linienfarbe über das Farbe- oder Farbfelder-Panel ändern.

Confirmed. V1 opens them showing the transparency. Placing this file in V2 gives no problem.

Kann nur aus eigener Erfahrung berichten ... Flyer, Poster, Panels, Handbücher, allgemeine Geschäftsausstattung ... sind bisher ohne Probleme gedruckt worden. Allerdings kann ich bei manchen "Design"-Entscheidung bei der Funktionalität der Apps nur den Kopf schütteln, aber immer noch um Längen besser als die allererste Version von Indesign. Aktuell bin ich bei V2 beim produktiven Einsatz noch vorsichtig, da diese Version doch arg mit Bugs belastet ist. Bei unkritischen Produkten teste ich V2 allerdings schon aus.

Correct!

Printing was correct, Preview was correct, but not the PDF. See attached image. Exported with Press Ready preset and layer visibility was done through the context toolbar. I attached the files also. layeroverride.zip