vonBusing

Yes, noticed that too 😩. One could think that this a very low hanging fruit that should be programmatically very easy to fix, but still not fixed in version 2.0. Maybe Serif will one day explain this incomprehensible choice.

+1 for the ability of linking to text in an external file (that can thereby be used by several publisher files). Supernice if markdown/html would be recognized for semantics, and a fantastic bonus if styling of the imported text could be linked to the document text styles (for example with matching html class attributes).

A tiny UI detail, but am I the only one always disturbed by the "Add new vertical/horizontal guide" icons on the Guide Manager panel being a page symbol rather than a more intuitive plus symbol?

Although I'm fully aware of the issue and know what I need to do, I get caught by this little issue regularly; especially when I'm in a hurry... It's a true time waster. A fix would be very appreciated.

Monthly mailer sound like some newsletter that could probably quite easily be handled by html/css/js. Any browser could make it to a pdf, if required.

Bump: Publisher 1.8.1 is still working the same way. If this is the intended behavior (not a bug but a feature), I would love to hear an explanation of this choice that I do not understand. If not, are there any plans to fix it?

Since it's an image (rather than a vector object) that you are recoloring, you could use the overlay layer effect to fill with an actual color, like white. Not sure how the fill property on an image is actually working, but it is some kind of tinting rather than fill that is occurring. Maybe someone will be able to explain the different color matematics between fill and color overlay on an image. They surely are different.

"Funny" that the Affinity Publisher internal update is less than 25 MB while the Affinity Designer and Photo 1.7.3 updates from the Mac App Store are over 400 MB, each. Does this reflect the actual update size for each application or is due to differences between distribution channels (Affinity Store vs Mac App Store)?

Please, please, please: let Publisher remember the last used Area setting in the export dialogue. The default is set to "All spreads", but I _never_ use that. I want "All pages". I do not know how many times I have to re-export my file because that setting is stuck on spreads by default, independently of all other export settings that are remembered very nicely. This is _so_ annoying...

Thanks @DWright for your reply. As one of the end-users, I'm not very familiar with acronyms like SSCM or GPO. We do have some central system to make software requestable for installation (that how I got AP and AD to be installed on the computer), but somehow, that require quite some preparation of the package to make it available (that I initiated). As far as I understand, the same manual preparation will be needed for each update to distribute. I was hoping this could be avoided if the apps were able to update themselves. Currently, we only have a very few installations (<10), so we are using individual licences. If interest is raising in the company and we get to a higher level, maybe that would justify some kind of multi-user license, but we are not there yet (although I try to be a good ambassador ). At the current level, it should not be a volume issue, that each installation updates itself.

Hi, In a corporate environment, users usually do not have admin rights on their windows 10 machines. With Affinity apps in version 1.6.x, it's not possible to update them once installed by an administrator, because they require a separate download and to run the new installation program with admin rights. My question is, if a 1.7.1 is installed, is the update procedure for future updates different and can be expected to be able to run on the app without an admin intervention?

I agree that locked items should not move in that situation. The behaviour you describe was already happening in Designer 1.6

Graphic for Mac does that.

I can imagine that connecting to a database is a slightly more complicated task than parsing a text-based file. Databases, and protocols to connect to them, comes in quite many flavours. One may also need to fetch data in several tables based on relations. It could still be more rational to let a more dedicated/specialised tool do the compilation to a file and upload that data to Publisher from the file. As an alternative to XML, I could see JSON as a well-established format when compiling not strictly tabular data. In my opinion, it is slightly more readable than XML, even for human eyes.

Hi, It's great that APub shows a notification when a linked file is changed. However, you cannot do anything else then, at best, cancel the message - if you ever get the time to do so: the notice shows up for just a very few seconds (I had to hurry to be able to get any screenshot at all). It could stay alive for a little bit longer. Also it would be great if the notification gave more helpful options like a link to the Resource Manager or even a direct "Update" option.