Wosven

Hi @JanFortune and @AdamCP and welcome. Did you test with the beta version? It's 1.10.5, so some bugs were corrected, and installing a Beta version won't mess your retail installations.

Please @My Strawberry Monkey, add your voice here :

You can add multi-channels colour for small text (it's better to have i.e. only black).

We did some tests here: But what would be interesting is to knowmore about the "larger discussion":

Bonjour @Piou, En fait, la commande fusionne tous les calques visibles en un seul au dessus du calque sélectionné (qui peut être parmi tous les autres). Donc il est logique que l'on puisse encore sélectionner les calques non fusionnés. Quelle serait la suggestion ? ====== In fact, this command merge all visible layers in one above the selected layer (and this one can be among the others). So, it's logical to be able to select the layers that aren't merged. What is the suggestion?

Sometimes, ID's files can be corrupted and bugged... the first reflex is to save as... and if it's not enough, we try export to IDML. This can take longer depending of the file. It's also possible opening the file or IDML with another ID version will correct the problem. I didn't looked at the resulting IDML, but it's possible it's checking and deleting any data or propertie unused by the document, or causing trouble, as a repair mode.

No. For example, you can have servers with folders like this: server/type of work (= booklet, books, magazines, etc.)/template by document (= a lot of folders) server/usefull/type (logo, recurrent pictures, documents, etc.) server for archives/year/client/type of work/specific document server for archives/year/type of work/specific document #n issue So you can have multiple pathes you use daily on different servers to get templates or usefull items, the folder in which you work on your computer, the server on which you archives or work/share files or export... And you'll have your own set of folders (local or shared) when working on files, until it's complete and you can exporty/archive them. That's why we ask the apps to memorise some paths globally (export, archive…), or by document's folder (open/import/save/save as...). Because when working on different documents in the same day, sometimes opening them simply to do minor corrections, or importing a new picture and exporting a new PDF, and closing the file... it's a pain to search where you exported this last PDF since the app use the previous document's path.

But perhaps one day... and it's not bad to think about how your files will be exported in different other types of file. It's sure we need some export abilities, toward plain text, document, or other DTP file format. Or some script possibilities.

Like anyone that dont have a dictionary available: you ignore it or you bug, if there's dependencies... But it's the same with Affinity apps-only features: they won't be exported, perhaps it'll be rasterised if it involve adjustments, etc.

@perfidious Can you correct your quote (you overwrite my text, I never said that), and just put the original text and your comment below it?

Yes, IDML, DOCX, XLSX, ODT, etc. are simply zip containing XML and other files to describe the content.

With an linked document, you can modify it annualy or punctually, it's like for logo: each time you open a document with this file imported, and it has been modified, you just need to update the link. You can have hundred of files using this linked file. Or you can have hundred of ads linked to a server with all the logos organized. A company have a new logo? Just modify the logo on the server, and check, if it's used in a file, that it's updated and get enough space on the document. If we had a way to have "colour profile blind" documents, keeping the exact values set for CMYK or Pantone or other predefined colours swatches, we could import those documents in other ones and export depending of the needed spec. And the convertion would only occur when exporting to PDF, like other apps do. For example, we use different types of paper for cover or inside paper in magazines, books or newspaper. Each time, I need to export or ask people to send me correctly exported ads with the appropriate profile. If I try to convert an already converted file, it'll be a mess, and the colours will be wrong. That's why it's important to begin with files with correct colours.

It can be something like this: 3Dpie.afpub

You've got previous answer in this thread: Now, about the collaboration part, if you only do simple files, like simple ads, without any special links, etc. No problem, it's possible to collaborate with someone working with APub. But for important work, like books and magazines using advanced features not yet — and probably never — in APub, it would be a complete mess to send back a file made with another app than ID. And certainly the end of a collaboration if people need to spend hours correcting your files to get back to a proper ID file. IDML is simply an archive (zip) containing XML files. The same as DOCX, XLSX... XML is fabulous for structuring datas. But ID exists for long, and there's a lot of data, and I'm not sure Affinity's goal is to produce apps and files reproducing such structure (this documentation, helpful for scripting, can give an idea): https://www.indesignjs.de/extendscriptAPI/indesign16/#about.html IDML is modified as some point, cf. different versions of the InDesign ExtendScript API linked above. Some variables can be renamed, or added, etc. Adobe don't mind people switching to the last version of ID, they don't want people using old versions. For now, it's only people writting scripts that shoud manage the difference between version. New datas are ignored when parsed by older versions of ID, and set to default. For example, between CS4 and CS5, they added individual values for round corners. If parsed by older versions, all the corner are square. If you need to maintain the visual effect, you'll have to use tricks. In the last year, I never saw a file made with ID version prior to 2014-2015 (and we were among the few that were using CC2014, instead of the last version). But I'm not a printer, and people here seem to use old versions. At some point, when everyone will need to upgrade the hardware, they'll have to do the same with the apps. I'm not sure what you mean by this. But if APub export to IDML, it should be usable files, without alterations, or it'll be bugged. At some point, a file going from ID > APub > ID > APub ... will be a total mess or unusable, or so simple — stripped of different values only used by the other app —, that it'll be better to redo a complete document in the appropriate app to use interesting and advanced features, than using a file reduce to simple and non manageable items (variables reduce to simple text, GREP converted to overrides, decorations not sticking to their paragraphes but reduces to curves, etc.). XML is a language, to share data. Microsoft and Adobe did a good job structuring their datas using XML, so now, other apps can read the files and convert them in their own structured datas. If it would be a good idea to develop their apps with this in mind, so their code can be easily translated to IDML, or IDML converted to their own code, I'm not sure it's the way Affinity apps are done. And working independently, give them more freedom, to search new ways to do things. But it can also lead to bugs, like we saw in another thread about SVG. If the apps are too different, and work in a completely different way it's difficult to output code created with other ideas in mind. How do you import or export features not yet implemented in a file format?

It's what we call in other app "negative", it'll invert the channels (the same way as it invert a mask: black become white, and white black) and the result look like a photo negative.

Ctrl+i will usually "invert" the colours. It's like a negative effect, or use to invert a mask. I'm not sure why you use it while painting. Shouldn't you simply use "I" if needing the colour picker? Or Alt to pick the colour below the cursor?

Doing research can help also: https://forum.affinity.serif.com/index.php?/search/&q=pie chart&quick=1

@ahnay Did you modify the title and deleted the content of this thread after getting an answer? Don't do this, now the title and the answers don't means anything usefull for other users, when it's the purpose of this forum.

Hum, each time you do one, you need to select again the export formats, etc. Being able to set this in a macro, or simpy having it remembering the last values would be helpful.

And an adjustment would rasterize the content, not really what we want for text. The not optimal but "best" way to do this would be, and if you only use PDF 1.4 to 1.7: to use an application palette in the footer document, and export this footer as PDF. to import the PDF in other documents, And use "assign" when needing a different profile in a document in which the PDF is placed. But it would be better if the apps were working differently with colour values and profiles.

If it's icons, it's possible you can download them as SVG. It would be more suitable for a web site to get them in this format.

It's an option in the Edition menu, with copy, paste, etc. For your problem:

The problem is more complexe, since it's also the way the clipping path work, it's different: The file corrected (17Ko): g62030967718039a3974574f67a8eb81a88f7b78584425d691fc477129b8de_AD.svg If you look at the code, Affinity apps are able to use this effect, but they do it in a messier way... Original file (5Ko): g62030967718039a3974574f67a8eb81a88f7b78584425d691fc477129b8de6651dc6a022b17b213fa3c469365e900050.svg

It's not a problem with the original file. It opens perfectly in Inkscape or a browser. The problem is the way Affinity apps interpret the content of the file.

Possibly, but we don't like it in France, and it didn't take. We nearly went from employees at the wickets to vending machines or web sites. I can remember an unpleasant moment, when trying to buy a train ticket from a remote location without Internet, and needing to do it on the phone. After few failed attempted calling this overpriced service, and giving the wrong answer in the last umpteenth questions, I ended up writing down the whole sequence of numbers, to avoid error and finalize successfully the call.