woefi

@anon2 Thank You so much! Strange tho, that it does not work, if you have selected a word to be replaced by the double-clicked field. In this stage as a beta feature, this is very counter-intuitive.

Sorry, I'm not sure if this has ever worked like I think it should – obviously some people have already managed to successfully do a data merge, so... I have a .csv file with headers called <name> <phone> ... a document with prepared text "<name>, <phone>" opened the data merge manager opened the fields panel set up all so that the datasets are correctly displayed in the fields panel If I press "generate" I get a new document with as many pages as my datasets but the text is still <name> <phone> I "accidentally" recognised the small grey text "double click field name to insert" but double clicking doesn't do anything... also no right click-menu or anything suggesting how I could mark my prepared text as "fields" How do you do it??

😱

that's how it should work. But as I mentioned, the colour palette panel still needs a lot of love from the affinity team - most times the swatch selection does not sync with the object selection...

I just saw: the latest beta (798) now automatically applies the colour swatch after it generated it as global! One step forward, hurray! So while they're on it: can we now please also select multiple colour swatches to delete them together? (renaming a colour is also very cumbersome...)

YES!

@Nazario not sure if I'm able to follow your example with the red/yellow triangle... But if there were an setting to automatically generate or link colours, you have to be able to have two or more equal colours that are intentionally NOT grouped together. example: I have some global white swatch used only for text on a dark background and the same white 0/0/0/0 but second global swatch for specific graphical objects. So I can independently recolour the text OR these objects as a whole if I'm changing the design.

Well, for AfPub, I would like this, but I realise it isn't just as easy: Glancing at the Adobe way(s), they never unified such a behaviour for InDesign and Illustrator as they grew based on different codebase. Illustrator mostly didn't need global colours and gave you the freedom of messing around creatively colour-wise. InDesign on the other hand does register EVERY single colour occurrence as a global colour, which is a more cleaner and maybe less creative way. ID way: For consistent output of press-ready PDFs, you want the controlled way as a Corporate Design usually never uses more than ten to twenty defined colours. (of which maybe 3 are absolutely critical) AI way: To create a (vector-based) drawing with thousands of brush strokes and multiple shades of colours and gradients you would not want to convolute your palette with all these colours as the colour perception is seen as a whole. (useless like giving a mathematician a list of all numbers available...) So Illustrator later got some features like "add all used colours" and "delete unused colours" to clean up your messy documents. Here Affinity tries to add all shades of colours including pictures, which isn't helpful at all and doesn't link the colour to its original object as global. Affinity now has the advantage of syncing the base technique between its three apps, but at the same time this exposes these short-comings in the different use-cases. Maybe a user preference in Settings could help, maybe a dialogue box...

Thank You for this suggestion, Walt. But that is basically the messy workaround which I now do, but like to avoid. What if you like to merge an object from Doc#A with some of Doc#B? The swatches have the same name and should be merged and linked together. At some point in every workflow you will inevitable have to copy objects together. In Indesign there is also this neat trick if you change a colour swatch definition and paste an object from an older document with the old definition (same colour name!) then the new definition is used and linked to. That's very handy! (...and can be confusing if you don't expect it, I know. But every merging process has to make decisions or put up a dialogue)

As the short title tries to explain: Copying objects with assigned global colour to a new document does not transfer the document palette. So they retain the colour, but the swatch lives a half life somewhere "in the air". That's a bug. Longer explanation: So I carefully manage my document with named colour swatches inside its document palette. ...maybe for a brochure for a specific client. Then I need to create a related document (same client, partly same graphic objects, obviously same colour swatches.) in a different size, say, for a business card design. So what you usually do is: select relevant objects, command+C, command+N for new doc, dial in all measurements, command+V Problem is, a new document has no document palette. And even if you create one from scratch, the copied colours are not appended to it. Further: if you then select "add current colour to palette as global colour" it creates a new name for it, although the old name was visible in the colour panel... I beg you, please consider repairing the underlying colour system in the affinity apps. there are so many inconsistencies. (create palette from doc uses rgb or hsl converted colours instead of the cmyk definitions, copying colours from one doc with cmyk OUTPUT colour profile a to another one with OUTPUT colour profile B does a colour conversion instead of keeping the INPUT values) I know, you know how things worked in ID/Pagemaker/Quark for the last twentysomewhat years

@Chris B I can confirm, what Old Bruce is saying: when you have no document open it crashes immediately after hitting the save button. Next time it opens, the preset is saved though. When I have a picture loaded, this does not happen. But when I choose "default" it crashes (with the opened picture). (I have my panels in separated mode!)

Wonderful addition in this 1.9 beta. At last you can save your studio presets!! Well, I tried and sadly it immediately crashed. (-> I have my panels in Separated Mode)

agree. And with many things regarding keyboards, it's very regional. and back on topic: I just realised, adobe indesign also uses the Edit/Delete Shortcut. But it's functionally separated from text editing, it flashes when deleting objects, but does not when deleting text. Which is why I suspect there is no distinction of these different modes within affinitys apps...

@Gabe Well I'm sorry I have to disagree, but that's like mapping the "a" key to a shortcut that inputs the letter "a". It's not the same as CMD+V, It is basic text input. I repeat: It is now OK. it works without flashing. If I reload the defaults. Before reloading there was a keyboard mapping, now it isn't. And it works, but doesn't flash. What I was wondering: I looked it up in the releave versions of the other apps, Photo and Designer, and there is still a keyboard shortcut mapped, which should be superflous. (Maybe a leftover=) It's no program error, just the app's keyboard settings are wrong. I manually changed them in the release versions and it's OK. (well, Photo is strange, though, as it flashes "Layer"...) also: As someone, who usually works with extended keyboards, I have to ask, why is the menu-item called "delete" if the delete key is not pressed, rather than the backspace-key...

Issue #3 is not fixed for me. Is there a newer beta than .651? It's not posted in patrick connor's thread. edit: I manually reset the keyboard shortcuts to "affinity defaults" and the "delete"-shortcut is gone. Backspace now works for me.