Jakob Winter
-
Posts
11 -
Joined
-
Last visited
Posts posted by Jakob Winter
-
-
This is still a feature I'd love to see. Would be such a smooth little trick...
-
I just learned about the trick of using a Gaussian Blur FX (instead of a live filter) to blur the edges of a layer I intend to use as a mask for another layer. It is an easy way of getting softer edges for a mask.
Sadly, this trick doesn't work on Masks. There I'd still have to use a Gaussian Blur live filter (which is somewhat cumbersome due to this bug...).
So, being able to apply a Gaussian Blur FX to a Mask would be amazing, particularly because it would remove one layer from the stack (since the FX lives on the layer itself).
-
1 hour ago, walt.farrell said:
I guess I don't understand why it's a problem to have to Release Mask before you can access the Gaussian Blur settings again
Efficiency. Its several unnecessary steps I'd rather avoid. And always remember, Affinity is jumping into the water with an extremely large fish (Photoshop). It'll always have to stand that comparisson if it wants to compete in a professional market. In some areas Affinity is doing an awesome job. In others, there's room for improvement
56 minutes ago, MEB said:As an alternative you can apply a Gaussian Blur FX to the shape
Wow, it even works with pixel images (not just with shapes). This is even more convenient for me than using a live filter. One layer less in my stack. Thanks so much. I'll use and teach that approach in the future 👍
Maybe it would be a good idea to add a feature request to enable the same for native Mask objects as well... its done!
-
By the way, in today's course I did a quick poll. 80% of them suffered from the above issue. So it seems its rather widespread...
-
Hey everyone,
I am experiencing this pretty annoying bug, where the children of a layer that is being used as a mask layer are not accessible anymore. When for example I want to dynamically feather a mask by using a Gaussian Blur live filter, I can only set the live filter as a child, if I move the mask to the top layer of the hierarchy. There I can drop the live filter onto the mask (to make it a child). When I then drop that mask onto an image, it behaves as it is supposed to, even dynamically blurring the mask if I change it. BUT I cannot access or change the settings of the Gaussian Blur (for that I'd have to move the mask back out again).
See attached GIF for clarification.
Is this a know bug? Quite a few of my students seem to suffer from it.
-
On 5/18/2020 at 6:27 PM, walt.farrell said:
"Drag" is defined (at least in Affinity, and at least on Windows) as "press left mouse button and move the mouse"
In that case, I used the term incorrectly. But my feature request remains the same.
-
On 5/20/2020 at 5:04 PM, fde101 said:
Try using only the right button to drag a file icon from one folder to another on Windows - not only will it drag the icon, but when you release the button it gives you a context menu asking what you want to do with it.
Awesome. Didn't know that trick!
-
1 hour ago, walt.farrell said:
You need the right mouse button to tell Affinity that you want to Add to the selection. But you still need the left mouse button because that button is what activates the mouse and initiates the action.
But why can't we use a Drag + RightMouse action? Surely the computer can register when the right mouse button is being pressed. Then the left mouse button wouldn't be needed.
1 hour ago, carl123 said:When using a brush, Alt + RightMouse on its own is already assigned and shows you...
Current Brush Size and Hardness
Brush Shape & Spacing
Brush RotationAh, I didn't know that. But Brush Size and Hardness are also displayed when pressing ALT + RightMouse + LeftMouse.
Brush Spacing and Rotation would be the perfect setting to use as secondary ALT action. Thanks for mentioning that! 😀
By the way, just to make my intentions clear: I am not trying to win an argument. I am just trying to get the logic behind the current behavior and - if possible - improve on it. And thus far I fail to see the benefit of the current behavior and would see my suggestions above as great workflow improvement.
-
Well, in the above cases the RightMouse button doesn't serve any other purpose. So using RightMouse + LeftMouse is completely unnecessary.
-
This is a tricky one to formulate, since it touches different tools (and at this point I can't even see its overall implicatins). So I am very much open to discussions
Right-Click vs. Right+Left-Click
Example 1 - Lasso Tool:
To add to a selection, you have to hold down Right + Left Mouse button. To subtract from your selection, you have to hold down the ALT key. The following thoughts pop into my head:
- Those seem like two different concepts (one using a modifier key, the other using some fancy mouse button magic)
- Why do I have to press two mouse buttons? Wouldn't one be enough?
The solution:
- Use Drag + RightMouse + LeftMouse to Add to Selection (as is the case today)
- Use Drag + RightMouse to Subtract from Selection
- Keep ALT as subtraction method too (for backward compatibility)
Example 2 - Patch Tool:
For the Patch Tool there don't seem to be any modifier keys at all - even though it uses a tool quite similar to the Lasso tool
- The Patch tool should therefore adopt the same modifiers as the Lasso tool (as described above)
This behavior (Drag + RightMouse = Subtract / Drag + RightMouse + LeftMouse = Add) could be adopted for pretty much all selection and paint tools!
The Same When Adding ALT
To change brush size / hardness, you can hold down ALT and RightMouse and LeftMouse and Drag (up/down for soft/hard and left/right for small/large).
- The additional LeftMouse is pointless. We could just leave it out (as in Photoshop)
- Maybe we can come up with an additional tool for using both buttons (e.g. Lightness and Saturation)
What do you all think? Is it a brilliant idea or have I overlooked something? Would love to hear your thoughts!
the layer system
in Feedback for the Affinity V2 Suite of Products
Posted
Awesome little trick. For me it has been a kind of ignorant trial and error operation to get a layer to drop at the right place. Simply knowing to move it to the left to not get nested is so easy - now my movements are purposeful!
Crazy, how tiny bits of knowledge can have such a great impact on one's workflow 😀