lepr
-
Posts
5,522 -
Joined
Posts posted by lepr
-
-
22 hours ago, Jamie88a said:
After searching many sources online I am confused why this simple object using three shapes as a box doesn't scale to show the white spaces as you can see on the left box example where it closes up?
Any help would be great. Thanks
The three shapes have a Contour applied by Contour Tool. For some reason, there is no option to automatically scale the width of Contour when an object is scaled, even when the scaling maintains aspect ratio.
To get the gaps between the objects to be scaled along with the objects, you will need to first bake the Contours, either by the Bake Appearance button in Contour Tool or by applying Convert To Curves command.
-
On 2/11/2023 at 9:03 PM, Omi said:
@Hangman, thanks so much for explaining that to me. You hit the nail on the head, and I really appreciate you taking the time to help me understand this.
I was confused by the gradient being in the form of a mask.
You haven't been given the correct explanation for the more saturated and warmer green being presented by the gradient node colour editor when you inspected the node.
It's true the mask is responsible for the gradient effect. The gradient fill has 5 nodes, all containing the same green CMYK [207, 62, 188, 21] definition, and so the fill itself is effectively a solid green and the mask acts as a transparency gradient, allowing blending with the underlying object's lighter green CMYK [175, 0, 155, 0]. All good so far.
The document has CMYK profile 'U.S. Web Coated (SWOP) v2'. When the app's default RGB profile (at the time of opening the CMYK document) is sRGB, the conversion of the aforementioned CMYK colour to RGB Hex should yield #298964. However, the node colour editor showed #2BB13D, which is a very different looking green in sRGB. A problem.
The explanation follows.
The gradient node colour editor initially opens in the mode that it was using when last closed.
When the node colour editor is opened and initially has the same mode as the node's stored colour definition, the value of the stored colour is shown, and switching the mode presents a correctly colour-managed converted value (without the stored definition being changed unless a slider is touched or a numerical value is edited).
When the node colour editor is opened and initially has a mode different to the node's stored colour definition, a simplistic non-colour managed conversion from the stored colour is presented, and switching the mode presents a value converted from that initially presented non-colour managed value (without the stored definition being changed unless a slider is touched or a numerical value is edited).
Your video shows the latter situation where colour management is absent in the initial conversion from stored value to presented value.
This has been a problem for years, probably since the beginning of Affinity, and it also afflicts the colour editor of FX.
-
1 hour ago, R C-R said:
Yes, that is what I meant about it being the same in both versions.
Yes, but maxegb is correct when he/she/they/? says v2 differs from v1. In the case of adding a new mask to an adjustment that is not itself mask-nested in something, the outcome is different in v1 versus v2.
-
46 minutes ago, R C-R said:
Why not just group the adjustment layers & apply the mask to the group?
Bugs in the rendering of masked groups still have to be fixed after years of reports. This thread isn't the place to repeat the details of that problem, so please don't ask.
-
50 minutes ago, maxegb said:
i do not have it [AP v1] anymore, so i will take your word for it. but being that i developed the habit of doing it without dragging anything, i think it was working. If not i would not find strange the actual behaviour. Unfortunately , i cannot check.
I have both v1 and v2. Automatic nesting of the mask in an adjustment works in v1 and does not work in v2.
Well, that's half the truth, lol
If the adjustment is not itself mask-nested in something, the new mask will be mask-nested in the adjustment, in v1 only.
If the adjustment is itself mask-nested in something, the new mask will not be mask-nested in the adjustment, in both v1 and v2.
-
10 hours ago, Shard said:
Two stroke tabs don't show up in the panel.
I guess you meant two stroke rows in Appearance panel.
The app currently will not add a second stroke or a second fill to a Text, Group or Layer, or a selection of multiple objects.
To what type of object were you trying to add a second stroke?
-
Ensure snap to spread is enabled and use Point Transform Tool:
- select line and star
- activate Point Transform Tool (F)
-
Mac: hold down ctrl key and drag a node of the line to snap to edge of the canvas
Windows: hover the pointer over a node of the line and read status bar at bottom of app window to get the modifier for 'to translate', then do the drag and snap to edge of canvas
-
22 minutes ago, Ralph Johann said:
Grouping should just put layers together in one folder to arrange everything more clearly and shouldn't affect the whole picture.
Exactly! That's what should happen when a Group has Passthrough blend mode (or 'Pass Through' in Photoshop). The name describes the expected behaviour.
Unfortunately, Affinity started with a dual-personality Passthrough and the developers have stuck with it despite many complaints in the forums over the years.
There is a hack that persuades Passthrough to consistently behave as expected: make the bottom object in a Passthrough group be white with Multiply blend mode, and cover the entire canvas with it. A white Fill Layer or vector Rectangle are ideal.
-
7 hours ago, NathanC said:
Having Colour LCD set on the display settings on an sRGB Affinity document colour picks from the UI correctly for me on my Macbook.
The bug has been in Affinity apps for many years, and probably from the beginning. At least it has on macOS. I don't know about the apps on Windows.
You won't see the problem when the document has sRGB profile, though, which makes sense when you consider the following paragraph.
When the colour picker samples outside the document view, the sampled RGB value is mistakenly transformed from display colour space to sRGB, instead of from display colour space to document colour space, and then that resulting value is used in the document colour space.
-
6 hours ago, NotMyFault said:
My replies are not intended to you post specifically, so no need to repeat these statements.
7 hours ago, ,,, said:I don't think it's a bug,
I disagree. You made your point. It is documented.
Oops, I thought a forum is a place for discussion.
-
1 hour ago, NotMyFault said:
1, 2 [...] 7
That happens because of the reason given in my first reply. I don't think it's a bug, although there clearly is room for improvement in how the software handles the situations of your examples.
-
48 minutes ago, R C-R said:
[...] I think it is a bug that it works only with alignment menu commands & not with the Alignment options on the Toolbar.
Maybe I misunderstand you, but toolbar alignments do make use of the key object, and the alignment popup of the main toolbar considers the key object to be the 'first selected' regardless of when it was selected.
-
5 minutes ago, laurent32 said:
Since we cannot see the status of that button
because it doens't stay grey when it is active [...]
For me using the app's dark UI, the button background is darker when enabled.
7 minutes ago, laurent32 said:And as @,,, says, is it "normal" not to be able (or not) to use that "option + select" method because of that option ? Is that a bug ?
To be clear, my opinion is that the status of that option should not prevent opt+click from being effective in the document view, and I've now reported it as a bug:
-
AD 2.0.4, AP 2.0.4, APub 2.0.4
macOS 12.6.3
Some functionality, for example Cut Curves With Key Object and aligning objects, make use of a key object. To mark the key object from amongst a collection of already selected objects, the user opt+clicks the object, either in the document view or in Layers panel.
If the option 'Allow selection to consider items inside a group' is disabled, opt+clicking is successful in the document view and in Layers panel.
However, if that option is enabled, opt+clicking is successful in Layers panel, but it is no different to just an unmodified click in the document view. Ignoring the opt key feels like a bug to me.
-
-
-
[deleted - was my misunderstanding]
-
[Deleted: grouping solution already posted by @anto]
-
AP 2.0.4, AD 2.0.4, APub 2.0.4
macOS 12.6.3
A folded row in the Layers panel can present up to three additional thumbnails of mask-nested objects such as Pixel Masks, Vector Masks, Adjustments and Filters.
Such a thumbnail of a mask-nested object usefully has a distinct red diagonal across it when the object is disabled, in the case of a Pixel Mask or an Adjustment, but not in the case of another type of object.
The lack of red diagonal when an object is disabled feels like a bug or oversight.
Related:
-
AP 2.0.4, AD 2.0.4, APub 2.0.4
macOS 12.6.3
A folded row in the Layers panel can present up to three additional thumbnails of mask-nested objects such as Pixel Masks, Vector Masks, Adjustments and Filters.
Shift-clicking on such a thumbnail will usefully toggle the visibility of the nested object in the case of a Pixel Mask or an Adjustment, but not in the case of a Vector Mask or a Filter.
The lack of response to shift-clicking a Vector Mask or Filter thumbnail feels like a bug or oversight.
Related:
-
9 minutes ago, Alec Sorensen said:
selecting the adjustment selected the group and then deleted everything.
In the version 1 apps, you must click the thumbnail, not the name area, of the mask-nested object (the HSL Shift Adjustment) to select only it and not its parent (the Group), and then delete it.
-
The Alignment popup in the main toolbar has target options including "first selected" and "last selected".
The Alignment Handles device, which can be enabled in context toolbar of Move Tool and several other tools, has a right edge handle for aligning the right edges of all selected objects to anything, and it observes many of the available snapping options.
-
-
51 minutes ago, Pšenda said:
A design flaw is that the enabled/disabled adjustment layer has no visual feedback in its thumbnail. When the layer is collapsed, it is not clear from the icons which of the adjustments are on and which are off.
It's made clear by a red diagonal line across the thumbnail of a disabled Mask/Adjustment in the collapsed row. At least that happens in the apps on macOS.
Color Changes When Copy/Pasted
in Affinity on Desktop Questions (macOS and Windows)
Posted
You're welcome!
Notice that I wrote, "The gradient node colour editor initially opens in the mode that it was using when last closed."
If you know that a gradient node has a CMYK definition, then ensure the node colour editor opens in CMYK mode. If the node colour editor opens in another mode, then switch its mode to CMYK, close it and then re-open it. Then you can switch mode and get a colour-managed conversion of the colour value.