Jump to content

Recommended Posts

Posted

🇬🇧 Hi, attached is a short video concerning the centering of objects: in one of them (the left one), there is a mask which partially obscures another object which overflows. The centering is not correct. I had never noticed this “indelicacy”!…

🇫🇷 Bonjour, ci-joint une petite vidéo concernant le centrage d'objets : dans l'un deux (celui de gauche), il y a un masque qui occulte partiellement un autre objet qui déborde. Le centrage n'est pas correct. Je n'avais jamais remarqué cette “indélicatesse” !…

  

Posted

A nicely made screencast for sure! :) 
(I'll look into the actual subject later…)

MacBookAir 15": MacOS Sonoma > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 18 > Affinity v2

Posted

You could make a transparent ellipse to encapsulate the eye design.

image.png.d71415661af37ce88080ac79b3c82f2b.png

iMac 27" 2019 Sequoia 15.0 (24A335), iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Posted

🇬🇧 Hi @firstdefence, in fact, what bothers me is that the calculation is done on plots not seen or on plots (like here) which are in a mask. This does not seem very “logical” to me and above all practical in use. But hey, your proposal is entirely valid, although it requires taking back the objects. And then, there remains the possibility of centering the elements by eye. 🙂

🇫🇷 Hi @firstdefence, en fait, ce qui me gène c'est que le calcul se fasse sur des tracés non vus ou sur des tracés (comme ici) qui sont dans un masque. Cela ne me semble pas très “logique” et surtout pratique à l'usage. Mais bon, votre proposition est tout à fait valable, bien qu'elle demande à reprendre les tracés. Et puis, il reste la possibilité de centrer les éléments à l'œil. 🙂

  

Posted
3 hours ago, sansnom said:

The centering is not correct.

The Transform Origin button is your friend! ;) 

MacBookAir 15": MacOS Sonoma > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 18 > Affinity v2

Posted
7 minutes ago, loukash said:

The Transform Origin button is your friend! ;) 

… together with the Alignment Handles.

MacBookAir 15": MacOS Sonoma > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 18 > Affinity v2

Posted
8 hours ago, sansnom said:

there is a mask which partially obscures another object which overflows. The centering is not correct. I had never noticed this “indelicacy”!…

It's odd in particular because of the bounding box for this group: it displays a square only, without an extended size for the nested 'MASK' layer. – In V1 I am unable to reproduce your offset alignment result.

squaredboundingbox.jpg.c704cc7f4854336cad0dc5bd0e7ddf18.jpg

Apart from this issue: What am I missing that I don't understand the need for your 'MASK' layer …

maskedellipses.jpg.a01d5a1d16187017692468db9b35f053.jpg

… nor how you made the darkest fill (bottom layer) appear outside the 'Mask' in your example?

maskedellipses2.jpg.a882ec5c054557469ab807037886269f.jpg

• MacBookPro Retina 15" |  macOS 10.14.6  | Eizo 27" | Affinity V1  
• iPad 10.Gen.  |  iOS 18.5.  |  Affinity V2.6

Posted

🇬🇧 Hi @thomaso, I realized this “indelicacy” while working on an illustration. For the video, I just created an example that summarizes the “problem”. If you watch the video carefully, you will understand how the two objects are created and their differences.
Otherwise, you have perfectly understood that the bounding boxes of ALL OBJECTS are taken into account for the centering calculation.
Finally, centering is by definition “visual”. We could then legitimately expect that this centering (and all other types of calibration) is calculated “visually” on the objects, otherwise, it no longer has any meaning or interest. And, in order for the centering command to apply effectively, being forced to modify objects also makes no sense.

🇫🇷 Bonjour @thomaso, je me suis rendu compte de cette “indélicatesse” en travaillant sur une illustration. Pour la vidéo, j'ai juste créé un exemple qui synthétise le “problème”. Si vous regardez bien la vidéo, vous comprendrez comment sont créés les deux objets et leurs différences.
Sinon, vous avez parfaitement compris que les boundings box de TOUS LES OBJETS sont pris en compte pour le calcul du centrage.
Pour finir, un centrage est par définition “visuel”. On pourrait alors légitimement s'attendre à ce que ce centrage (et tous les autres types calages) se calcule “visuellement” sur les objets, sinon, cela n'a plus aucun sens ni d'intérêt. Et, afin que la commande de centrage s'applique efficacement, être obliger de modifier les objets n'a aussi aucun sens.

  

Posted
1 hour ago, sansnom said:

For the video, I just created an example that summarizes the “problem”. If you watch the video carefully, you will understand how the two objects are created and their differences.
Otherwise, you have perfectly understood that the bounding boxes of ALL OBJECTS are taken into account for the centering calculation.
Finally, centering is by definition “visual”. We could then legitimately expect that this centering (and all other types of calibration) is calculated “visually” on the objects, otherwise, it no longer has any meaning or interest.

Sorry, in my previous post I have misread your video! (in particular: the 'MASK' layer's x/y position on the page)

Now, after recreating your layout & layer hierarchy in V1, it appears that V1 creates a the bounding box for a Group + nested "Mask" layer differently than V2:

While your V2 video shows the bounding box of the selected Group layer as a square tight around the masked result (which, imho, appears as a V2 improvement) …

ellipsemaskgroupedV2.thumb.jpg.e1dd49df0385c3ba2ee4a1547bbb0f8e.jpg

… to me in V1 the bounding box of the selected Group layer is extended by the size of the masked ellipse layer. The layer type "Mask" nested in a "Group" seems to cause this different bounding box, not the offset ellipse layer only:

ellipsemaskgrouped.jpg.d36d746202b41490ef2d1519ef3986a2.jpg

2 hours ago, sansnom said:

And, in order for the centering command to apply effectively, being forced to modify objects also makes no sense.

I fully agree, the displayed bounding box should be reliable and work with its displayed size for alignment, too. Also the user should not be forced to a different workflow just because of a feature/tool not respecting the displayed bounding box.

Nevertheless and just as a suggestion, this specific visual result may get achieved with a less complex layer hierarchy and, for instance, just 3 "Ellipse" layers, without "Group" or "Mask"), not causing the bounding box issue.

ellipsesonly.jpg.e20a6cac0c41e48244956b7813f7c0d3.jpg

• MacBookPro Retina 15" |  macOS 10.14.6  | Eizo 27" | Affinity V1  
• iPad 10.Gen.  |  iOS 18.5.  |  Affinity V2.6

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.