lepr

Increase the Mitre value in the Stroke panel

@Dan C: the reply from KCP to me that I see is "Thank you for the response. It worked."

RGB(138, 66, 153) would be the numerical value for the purple colour in Adobe RGB colour space, so I wonder why Photoshop is telling you that is the value in sRGB colour space.

In that case, there is a failure of the ICC Display Transform. I remember at least one report of that on a Windows computer a few years ago. If the ICC Display Transform was working you'd see a big difference with it enabled versus disabled. If it was working, the view of the 32 bpc linear image in Develop Persona would appear brighter and match the view of the 16 bpc gamma encoded image in Photo Persona.

Your dodge mask is mask-nested in the curves adjustment, whereas your burn mask is clip-nested in the curves adjustment. A mask-nested thumbnail appears alongside the parent's thumbnail when the parent is folded, whereas a clip-nested thumbnail does not. Drag and drop the burn mask thumbnail on its parent's thumbnail, not the parent's name, to mask-nest it.

As I already said, if the container (a Layer in these cases) has been transformed after the objects have been put in it, a subsequent Move Inside will involve a miscalculated transform. My video showed that happening. Maybe I should have added a superfluous statement that if the container has not been transformed after the objects have been put inside it, a subsequent Move Inside will involve a correctly calculated transform.

A key object can be nominated for the alignment. After at least two objects have been selected, opt/alt-click (in the view or Layers Panel) one of them to mark it as key - its highlight will be thickened in the view and become brighter in the Layers Panel.

It's slightly different because you have Windows and I have macOS. Looking at your screenshot right now, the options you describe are in the Renderer control, not the Retina Rendering control that I told you to change. Immediately under that in your screenshot is Retina Rendering: Automatic (Best). That's the one I clearly told you to change from Automatic to High Quality. I even posted an image to make sure you couldn't miss it!

Yes, I misunderstood. I have made edits to a couple of posts a few minutes ago and added an apology to you in one of them. Sorry.

Thanks for the suggestion. I've made the edit now

[deleted]

Yes, and after I realised that, I clearly stated that cmd-drag could replace ctrl-drag.

I've noticed today your bug has been reported a few times by iPad users, therefore it seems to be a problem on Apple Silicon devices but not on Intel devices.

The thing that's clear to me in many discussions is that what you think I'm saying, and what I am saying, are often complete opposites. Here we have a prime example. I did say ctrl-drag can be changed to cmd-drag as part of creating a more Mac-like experience. My precise words were: "Cmd-dragging a node could do what is currently being done by ctrl-drag, obviously."

The Dell monitor will be classed as a 'Retina' pixel density device by Affinity and so the document view rendering is affected by the Retina Rendering control in the performance settings of the app. The flickering should stop if you change that control from the default 'Automatic' to 'High Quality' then relaunch the app. (The Asus monitor won't be affected because it is not classed as a 'Retina' device.)

OK, I'll bite - you could be serious. The discussion has arisen because the Node Tool incongruously uses ctrl key where cmd key would make more sense in the Mac world and would match the Mac cmd == Windows ctrl found elsewhere in the app. Cmd-dragging a node could do what is currently being done by ctrl-drag, obviously.

Thanks for the file. The join happens without weirdness in AD 2.1.1 on my Intel iMac (macOS 12.6.9). join.mp4

Please do start a new topic.

[deleted my misunderstanding] Apologies for rudeness to R C-R.

It's unused in Node Tool in v2.x, also. My money is on a mistake or thoughtlessness, originally, rather than a deliberate avoidance of its use. However, there might now be a deliberate maintaining of the situation.

[removing this paragraph] Ctrl-drag would not need to change. Don't confuse dragging with clicking. We've been talking about ctrl-click. We've already discussed sharp-to-smooth: make it be cmd-click instead of ctrl-click. [adding this paragraph] In the same fashion, make cmd-drag replace ctrl-drag. This thread is about to be wrecked. I can feel it.

I'm getting the impression that your placed 'Border' SVG files are linked, rather than embedded, and therefore there will be an unwanted changed appearance inside the parent Affinity document if the external files are edited. The app's Resource Manager will say 'Linked' or 'Embedded' on each line of its content. If I am correct about your placed files being linked then, still in Resource Manager, select all of them and click the Embed button at the bottom of the manager. They will become embedded and then will not be affected by future edits to the external files. By the way, each Affinity document has a placement policy. You can choose to prefer embedded or linked in the Document Setup so further imports are as you require.

Possibly there is a bug. Often best to attach a document (in the state before doing the join) for examination, otherwise multiple incorrect guesses could confuse matters in addition to being a waste of time and effort.

I don't know (and not going to search for one LOL)

It's a known bug from v1.x. Attached is another simple example in a v1.10.6 document. Move Inside bug.afdesign The video shows the outer container (it can be a Layer/Group/object) crucially being transformed after the other objects are put inside it, and then the subsequent 'Move Inside' which involves a miscalculated transform. Move Inside bug.mp4