Clicking inside empty rectangle selects the rectangle

[jvns]

When I click inside an empty rectangle (with no fill), it selects the rectangle. It's not consistent though:

1. If I click on a text object inside the rectangle, then click in an empty area inside the rectangle, it selects the rectangle
2. BUT if I click on the text object, click outside the rectangle (to deselect it), and then click on the same empty area, it doesn't select the rectangle.

I'm using version 2.6.0 on desktop.

Is there anything I can configure to make clicking inside the rectangle NOT select the rectangle? I have “Select object when intersects with selection marquee” turned off already.

I've attached a video to show what I mean.

 

 

.

[GarryP]

It can be difficult for us to diagnose problems if we can only see a small area of the screen.

What happens in the software can very often depend on may different options/settings which are either ON or OFF.

Can you show us the whole screen (whole application UI) in a video so we can see, in particular, how your layers are organised in the Layers Panel and what options you have in the Context Toolbar?

[jvns]

Sure, here's a screen recording with the whole screen and with the Layers panel! I checked and the order of the layers doesn't affect the behaviour.

Edited March 18 by jvns
layers

[GarryP]

Thanks for providing the new video.

I can replicate the same thing, as far as I can follow along, in Designer 2.6.0 on Windows (with or without an Artboard).

I tried to replicate it in Designer 1.10.6 on Windows and got a different result.

I think the difference could be a change to how on-canvas layer selection works which was implemented at some point in V2 but I can’t think what it was off the top of my head or what was given as the reasoning behind it. (I think it was to do with the “Auto-select” settings, or something related to those perhaps; maybe that helps someone to figure it out.)

Hopefully someone whose memory is better than mine will be able to explain things.

Without knowing for sure whether this is by design or not I can’t say whether it’s a problem or expected behaviour, and I don’t know whether the current situation is ‘better’ than it was in 1.10.6 in this regard. (I might have found it to be very useful but simply not noticed that it was happening.)