fde101

Personally, I do not have an immediate use for either one (IDML import or export), but I still recognize having both of these as being a significant advantage if the product does eventually include this. It helps to future-proof documents created in the program as it provides for two-way exchange with a known format that could then be read or created by other tools. This would not only be of benefit not only for exchange with other layout applications, it also opens up the possibility for specialized programs to perform specific tasks that may not fit into the normal workflow of a layout tool. That can easily be a big selling point as not many layout applications currently offer this.

Actually, the booklet feature works perfectly for top-fold cards. When you create the document, turn on facing pages and set them to be arranged vertically starting at the bottom. Set the printer to flip on the short edge if it has a duplexer.

Set a custom page size of 5.5" x 8.5" and make sure there is an even multiple of 4 pages in the document. In the print dialog (File->Print), set the paper size to US Letter, then in the Document Layout section (on the Mac, use the popup menu directly underneath the paper size control; may be organized slightly differently on Windoze), set Model to Booklet. Use the printer settings to configure duplexing appropriately if you are printing. You can then print or export the PDF from there. In theory, this is just a booklet of four pages (front, inside top, inside bottom, back) printed to cardstock... Again, the page size of the Publisher document is the size of the finished page (after folding); the size of the paper set in the Print dialog is the size of the actual sheet of paper it is being printed on. However, a top-fold card may present a problem with the set of options currently available for imposing under Publisher... I will need to play with that a bit more later on; this is a use case I hadn't really thought about before... side fold cards should be trivial using the booklet feature, but I'm not sure if the current booklet feature can adapt to a top-fold scenario... hmm...

This is a really bad UI design. Suggest renaming the "Cancel" button to "Revert" and eliminating the "Done" button. Also, "Done" is not a verb and should not be the name of any button regardless.

On the Mac it would be PDF now. Not sure what Windoze is using these days...

A limited form of this is available now via the Print dialog. There have been many requests to also make this functionality available from the Export dialog, but so far that hasn't happened.

They don't support export to the XPM, NEO or ILBM formats either. How lame is that?

Hi @markjmcg, welcome to the forums! The Serif range is NOT being "rebranded" - the Affinity range of applications is entirely new, not an updated version of the older Plus line, which has been discontinued. So far indications from Serif have been that they do not currently plan to introduce an HTML/web publishing solution within the Affinity product line. This has been discussed previously on the forum.

Even in Publisher the Hyphenation option in the Character panel does not enable hyphenation. It allows the user to override the language whose hyphenation characteristics are used when hyphenation is enabled using the options in the Paragraph panel: The options to enable hyphenation are completely missing in Photo and Designer, but if you open a document in one of those programs which had hyphenation set up in Publisher, you can change the language whose hyphenation rules are applied for a specific region of that text - for example, if you edit the text itself and add a phrase from a different language in the middle of an existing hyphenated paragraph.

Yes, the Affinity team from Serif does read these threads; they do not usually respond to feature requests, which is the section of the forum you are in. https://forum.affinity.serif.com/index.php?/forum/71-bug-reporting/

In the interim, you can select an object from inside a group by command-clicking on it (Mac - not sure what the Windows key is for that, maybe control?). After that you can directly select other objects from within the same group.

As @Pšenda pointed out, gradients applied to a pixel layer are rasterized when switching tools, and no longer editable. The screenshots from @JeffreyWalther show a gradient being applied to a pixel layer, which prevents further editing. To make this work, create a shape instead (rectangle or whatever) and apply the gradient to the shape. Then you can edit it by selecting that shape again when switching back to the gradient tool.

@aztx, welcome to the forums! The ability to resize the window would be nice too. Note that the specific use cases you mentioned could probably be accomplished using LUTs, which can be imported already. If you are trying to bring curves in from another Photo document/instance, try adding the Curves adjustment layer from the source document to the Assets panel; you can then drag it into another document from there - also, assets can be imported/exported.

This sounds like a better fit for Designer using artboards (which can be named) as you can also use symbols to keep the common elements in sync

This is what tabs are for... I do tend to agree that the dialog could stand to be re-organized a bit.

I would rather this were a popup without the buttons, and would stay open until you clicked outside of it, similarly to the popups for changing stroke attributes and the like from the context toolbar.

Adobe's camera raw is not really part of Photoshop, but is a separate tool that happens to integrate with it. The ability to work with metadata/"sidecar" files is thus a function of camera raw rather than of photoshop. If you actually pulled the developed images into Photoshop they would become PSDs, without the metadata files. Affinity Photo's develop module is part of Affinity Photo itself and produces layers within the native Affinity document; it is not separated the way that photo raw is. The functionality you are asking for would not be appropriate for this type of application, but should be a separate tool. The Affinity team may potentially release such a solution at some point in the future, which would indeed be a separate application from Affinity Photo - this has been discussed at length on other threads, repeatedly, because people seem to post new threads for this several times a month. Until then, what you are looking for is not an editor (as Affinity Photo is) but a dedicated RAW developer / DAM-type tool, such as On1 Photo RAW, Capture One, DxO Photolab, etc. You are unlikely to find something that can read the adjustments from camera raw's sidecars (XMPs) as that is a completely nonstandard use for those files, but most of these other products can work in a similar manner, just with their own sidecar formats. Capture One supports metadata from XMPs but I don't believe it will handle adjustments from them.

No. As explained on another thread, they are converted to embedded documents upon import, then flattened to simple layers if exported back to PSD format.

Hi @Lily Seipp, welcome to the forums! This is already available: Note that there have been some complaints from people getting less than satisfactory results using this feature, but there are improvements being made on this for version 1.8, the desktop versions of which are currently in beta.

This is optional in Affinity Publisher. If you set the section to "continue page numbering" then this does not happen. Doesn't seem all that complicated... though granted it does require extra steps compared to simply naming the page. Again I don't see anything wrong with the request, and it would probably be welcomed by various other users, I just don't see it as something essential to the program. That seems like a reasonable way to visually mark which masters are applied to which pages, at least until you start accumulating a large number of master pages and can't tell the colors apart any longer... but if done that way, you are in essence using the colors to "name" the master pages, so applying colors to the individual document pages as well might lead to more confusion than utility. You would need a clear way to distinguish within the page listing which colors represented the pages themselves and which ones the referenced masters. I don't think I like the idea of using colors for both.

That one at least on the surface seems to be a bug, but I would need to look at it more closely when I can find some time later on.

Fair point - if the distinctions encapsulated by that other thread were meant to be included by reference then this is actually a duplicate of that other thread and should be merged, locked or deleted.

I'd say that is kind of telling... this is not a "needed" feature, not really essential. It is not a bad thing to ask for by any means - but it is a want or a potential convenience, not really a need, at least for the vast majority of users.

Not so sure about that. InDesign can't do this either (people are asking: https://indesign.uservoice.com/forums/601021-adobe-indesign-feature-requests/suggestions/31462438-add-ability-to-name-individual-pages-just-like-w). QuarkXPress lets you name master pages, but I don't believe you can name individual document pages.