Selecting texts - problematic

[ziemowit]

Hi,

selecting texts in AD 2.0 is very annoying. If you want to select the smaller one, you basically need to click nearly above it, please take a look: 

 

Is it a bug or was it meant to work like that for some reason?

[Chris B]

Hey ziemowit,

If you swap the layer order around, it doesn't seem to happen. However, I have just checked V1 and the layer order doesn't matter - I feel like this might be a regression so I'll log it with the developers.

[ziemowit]

thanks for your reply, well to be honest you can't work with that. Designing a website and working in a zoom-out view makes it so problematic, that I would rather stick to the old AD:-S

[Chris B]

It's logged with the developers so I'm hoping they can resolve this very soon.

[ziemowit]

cool, thanks for your input;)

[loukash]

@ziemowit see this thread to understand what's happening and why, and how to work around it until the bug has been fixed (hopefully):

 

[ziemowit]

Hi loukash, 

cool, many thanks for this;)

[ziemowit]

although I tried option-click - in my case it's even worse than cmd click;)

[ziemowit]

Hi, any update in that matter? I can see that the recent update didn't fix anything:-s

[DylanGG]

Noticed this as well. The "hitbox" around text is much larger than the actual text itself. Update 2.0.3 didn't fix it.

[MikeTO]

2.0.3 fixed the biggest problem with the "hit box" (selection zone) of text objects being too large. The release notes state this issue was fixed: "Hit box of scaled text could be incorrect".

The remaining problem is that the hit box includes the cap height of the first line of text which is above the text object as well as the advance (built-in space), although the latter is more minimal. I posted a blown-up example of this remaining issue in this thread.

 

[Affinity Info Bot]

The issue "Layer order affects object selection" (REF: AFP-5621) has been fixed by the developers in internal build "2.2.0.1900".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.