BofG

The browser is colour managed, that's why it looks correct there. Have a read about profile connection space, basically it's a defined "real world" set of colours that are mapped to/from so all devices show the same thing. Photos doesn't use it, so your colour values in your file aren't mapped to their "real life" colours before being sent to the monitor.

Photos in Windows isn't colour managed - I *think* it uses the display profile "as is" so if you do have a wide gamut monitor then it will as mentioned above come out over saturated as the rgb values in your file go further in the monitor colour space than in the file's defined profile. If that makes sense. Which maybe it doesn't. Hopefully someone else will be able to explain it better If you open your image in a browser does it match your Affinity display?

Borderless printing got broken somewhere around the 1.9 release. I think your only option is to export your file and print from a different application. Edit - seems like it was v1.9.2. If you bought from Serif you can install the older version again.

Is it just me, or does that look like an undocked window going a bit awry? I can't see the filename or close button. Is there a way in the app menu to restore the windows to be docked?

I suspected that might be the case, it's a shame as it would be so helpful in this situation. Thanks for the help. Now, maybe if I plug in two mice at once.... 🙃

Is it possible in Designer to select two nodes, and then when altering the control handle of one have the other move exactly the same? I'm trying to learn isometric techniques and to fit both edges of a front face to a side curve would be so easy if I could drag two node handles at once.

Everything works for one person, but there have been more than a few people posting here dismayed that all their hard work has to be redone because the output is rasterised. In some cases the rasterisation can lead to unintended side effects in some formats (e.g. pdf where a nice crisp vector is suddenly an anti-aliased edge at a low resolution). If the person understands from the start what the approach means for the possible output that cannot be a bad thing surely?

It's a different approach entirely. With the base text (not converted to curves) you add a layer effect. At the foot of the layers panel there is a small "fx" button - inside the list that shows is the "outline" mentioned. Be aware - effects ONLY export as raster (aka pixels) and can cause elements the layer overlaps to also rasterise. If you need a "pure vector" export then stay away from these.

Convert the text to curves, then combine the curves using the boolean add.

This should just be the norm, not a workaround. Printing from Designer is so flaky, always has been.

Hmm, combine (Boolean add) shouldn't be creating a hole. It's a bug isn't it?

Try either changing the layer order (so put the rectangle behind the circle) or select both layers and choose Layer > Geometry > Merge Curves before you combine them.

In that case my original suspicion is probably correct. It is an annoying aspect of Designer, personally I feel that anything that would result in rasterisation should only be accessible from the pixel persona. You aren't the first person to spend time working on something only to see it not export like expected once finished. There might be some things you can change in the file without too much effort to get the export you want. It will be those blend modes and layer effects that need looking at.

I should point out that this was just my thoughts based on looking at your image on my phone. Without having the Designer file to look at properly I can't say for certain. Does it look identical if you export as a full raster image like png?

These cause rasterisation on export, which looks like it's causing the issues. You can try setting "Rasterise: unsupported properties" to "Rasterise: nothing" and see if you get lucky. Other than that you would need to look at the Designer file and remove those blend modes and effects and make them in a different way.

I think you need to switch to the pixel persona and then ctrl or alt click the layer. I forget the exact details. You will need to combine your shapes first as you cannot add to a selection.

This happens when there is a conversion from one profile to another. If you create your document in "cmyk profile a", set your k-only black and export to "cmyk profile a" your black won't be altered. If your export to "cmyk profile b" then there will be a conversion and your black will end up as four colour.

That's not possible, but it actually is correct to not be possible as the x-4 spec requires a profile for the output intent.

It has never worked, maybe one day....

I'm stuck in the past on v1.8 so cannot open the file - does it contain anything that is getting rasterised? If native svg is "blurry" then there are issues elsewhere... I find a good lens cloth works well sometimes :)

Try moving the "y" layer below the "a" layer before you add them. The Boolean operations often leave a lot to be desired.

I guess it makes me redundant

Both good points. I've held off updating to 1.9 because I don't know what new bugs await and not sure if the little annoyances from before are fixed. I've decided it's better the devil you know. There is a "known issues" sticky, but it's far from comprehensive and only lists things that they have fixed (as in introduced in 1.9 and fixed). A public bug tracker could have it's downsides, more pressure on the no doubt already stretched team, but I think it would be a positive step for the users.

I'm not sure on the specifics, I've just pieced together this from what little has been said and some of the developer info from Apple that mentions JavaScript engines and that JIT flag. It's a pity there isn't more detailed official information. Wholeheartedly agree with this. I think the test plan is somewhat ad-hoc at best. I've been using the software long enough to have seen a few of the major releases, and I now double check every now and then to ensure automatic updates are not enabled.

In a different thread they said this slow start up is down to them embedding a browser in the app, which is used for the welcome screen and user account. I believe it allows them an easy way to keep those parts updated, as they can just put fresh html content on the server and the app will fetch and display it. The new Apple malware check is more intrusive in this use case as the app (via the embedded browser) has a JavaScript engine and can execute arbitrary code.