loukash

Another non-destructive possibilty is to group (blue) the Outer C donut objects (green) while making a copy of one donut (red), giving it a simple solid opaque stroke, and adjusting its width and angle and mask the blue group with it: If the export should be more "vector", then you may want to expand the stroke mask to regular curves so that the mask remains a vector curve. Otherwise masking with a stroke will rasterize.

Nope. Yep.

Example please!

Example please.

@Stepaan's post was exactly about the specific regex pattern not functioning correctly in v2. While I have initally stated that it "works for me", at that time I have only checked the "find" part of the search, not the "replace all" part. The latter appears to be broken in v2. It has nothing to do with the Czech dictionary as I'm using it already. It looks like you have pasted the wrong links…

Just recently I have received a JPEG QR code to include in a layout. I needed it in vector but the client had no clue how to do it, or possibly even what the heck I was talking about. So I had to actually scan it first to get the content as plain text, then paste it into an online QR code generator, download the vector, double-check if the text is still correct, convert to K100, etc. The Publisher "Text Wrap" workflow would have been way faster. And unlike any of the image tracing tools that I'm aware of, it will trace it precisely. So to each their own. In that sense, I consider this "happy accident" Publisher tracing tool a kind of "one trick pony". It is severely limited, but in some instances it can be exactly what's needed.

Because: Designer was the first app of the bunch, released in 2014 before there was Photo, and there was the idea to have basic pixel editing capabilities out of the box. Designer is effectively the most "universal" of the three apps, as it also has pretty good typography features, and with artboards it can even somewhat emulate a multi-page layout. As such it is also a pretty good "jack-of-all-trades" app for novices, hobbyists and occasional "tinkerers" that don't want to spend their money on the whole suite. But yes, if you also have Photo, then File > Edit in Photo (and then back the same route again) is the better – and intended – workflow.

That all said, strictly speaking there is a "bug" in that the "Expand Stroke" menu command should be grayed out, unless "Solid Pen with Pressure" is selected.

Neither. "Vector" brushes are actually pixel patterns attached to a plain vector curve. That only means you can change shapes or the brush patterns later, unlike with Pixel brushes. But since Affinity doesn't have a built-in image tracer *) you can't expand them out of the box. The only true vector brush is the topmost one in the Pens category: "Solid Pen with Pressure", and correspondingly also the Pencil tool with Controller enabled, as used with tablet pen pressure or with mouse pointer/trackpad velocity. Those can be converted to outlines. *) As it turned out just recently, there is a very rudimentary image tracer in Publisher, so as a workaround it is somewhat possible to convert at least some of those "vector/pixel" brushes to vector shapes:

It would be nice if it actually would do that, but from my testing, it averages about 1 node per 8 pixels. Which is obviously more than enough for the actual functionality, i.e. Text Wrap. Hence my hint in that thread, that "the more pixels, the better result". I've tested with images scaled up to something like 100000×100000 px (yes, Affinity can handle up to 256000×256000 px), and it can make a difference. I consider it the best QR code vectorizer from all that I have used so far. Its deficit of being limited to using straight lines in strict 90° angle is the feature in this special case.

As it turned out, this – surprisingly – not true:

No offense, but I really don't understand your workflow here. If your v1 documents have been saved to an iCloud or a local folder – i.e. one that is also visible in the Files app – you don't have to import anything. When in Affinity v2, just navigate to that folder and open the document you currently need.

Some of this functionality is covered by "Power Duplicate": affinity.help/designer2/en-US.lproj/pages/ObjectControl/duplicate.html

If you have Photo, you can relink almost everything: File > Edit In Photo open the Links panel select the detached object inside the affected Symbol group (the was the object with the dashed vertical line in Designer's Layers panel) see the Links panel which attributes are detached keep the selection, but drag one of the corresponding instances of the object to the detached attribute well in Links panel to relink that attribute (see affinity.help/photo2/en-US.lproj/pages/LayerOperations/linking.html on how linking works; it's a bit counterintuitive workflow that may require some "rehearsals" first…) File > Edit In Designer to get back where you came from voilà ADe's Symbols, APh's Links and even APu's Master Pages obviously use the same underlying technology.

let's say you've been working on "My layout.afpub" enable Save History With Document Save As: "My layout with history.afpub" disable Save History With Document Save As: "My layout.afpub" to restore your original version

There is a simple trick (a bug? a "happy accident"?) to reverse the stack order of objects, including artboards: Add a blank layer to your document. By default, it will land inside one of your artboards. In the Layers panel, pull it out on top level and place it at the bottom of the stack Select all artboards. Layer > Arrange > Move Inside Layer > Arrange > Move Outside voilà

There is a simple trick (a bug? a "happy accident"?) to reverse the stack order of objects, including artboards: Add a blank layer to your document. By default, it will land inside one of your artboards. In the Layers panel, pull it out on top level and place it at the bottom of the stack Select all artboards. Layer > Arrange > Move Inside Layer > Arrange > Move Outside voilà

The issue discussed herein is that the same regex pattern is not giving the same result in v2 on Replace All. See @bajqo's screencast.

The copy is likely not aligned to the pixel grid of the document. That will introduce antialiasing. Make sure "Force Pixel Alignment" is on, and "Move by whole pixels" is off.

It will be a new image file, not "Untitled" as from Acquire Image. The major difference is that you can select the format you're scanning to and define the file name before scanning. If you're scanning to TIFF (or PNG, unless your scanner support features that PNG can't do), the scan will be just as lossless as with Acquire Image. I'm seeing this with the HP (LaserJet MFP M28w) as well. It's connected via AirPrint. The error usually appears when the MacOS "advanced" Network settings for some unknown reason disable IPv6. So I have to enable IPv6 manually again, then it works.

Hm, that's all negligible. Affinity just plugs into the existing MacOS API. The thing is that apparently they messed something up on the way and can't figure out what exactly. In fact you can "close the circle" so to speak, and make use of an Automator Quick Action to open Image Capture directly from Photo via the Services menu – and thus also available via keyboard shortcut. So in the end, the workflow will be virtually identical to the Acquire command, except that it actually works. And it works like a charm.

Actually strike that idea with Automator! It's in fact much easier: in Image Capture, open the Scan To popup menu and select Other… navigate to your Applications folder choose Affinity Photo as your "scan to" app scan That's all! As above though: make sure to Save As or export into a directory of your choice, as the temporary folder where the interim scan file resides will be eventually cleared.

This is a known bug which the Serif engineers allegedly cannot exactly replicate. Acquire from Affinity works for some users, but not for others. All of my three compatible scanners – 2 Epson and 1 HP – are affected, both in Affinity v1 and v2. All three work otherwise. Scanning via Apple's own Image Capture app – which is technically exactly the same process – works always fine. So simply use that instead. To scan via Image Capture directly into Photo, you can create a totally simple Automator plugin, which will pass the scanner input (that is being temporarily saved in a hidden system folder) to open with Photo: Open the Automator app, create a new Image Capture plugin and add at least the Run AppleScript action. Make sure it contains exactly this code: on run {input, parameters} tell application "Affinity Photo 2" activate open input end tell return input end run Save the plugin under a meaningful name like "Open in Affinity Photo" or whatever you like. It will be automatically saved in ~/Library/Workflows/Applications/Image Capture Then open Image Capture, select your scanner and set the Scan To popup menu to the name of your previously created plugin: Then scan. That's all: Make sure to Save As or export into a directory of your choice, as the temporary folder where the interim scan file resides will be eventually cleared.

Um… it's complicated. It may appear counterintuitive, but "Move by whole pixels" should be off unless you have a specific case where an object must be off the grid by a defined amount, e.g. 0.5 px, and you don't want it to snap back to integer pixels. Thats because "Move by whole pixels" overrides "Force pixel alignment". In general: "Force Pixel Alignment" on "Move By Whole Pixels" off Decimal Places: 6 (especially pixels) Transform panel: keep an eye on it all the time

I agree with that. Too much "granulation" isn't always the best thing. Let's talk about that in 8 years…