Option + Drag not working in 1732 to begin lasso node selection

[dcarvalho84]

Option + Drag is not letting me to make a selection for nodes.

The "simple" drag is working, the option + drag is not, at least for me.

Mac OS Ventura

[tudor]

Same here.

[Hangman]

FWIW, it's working for me in Monterey...

[MikeTO]

It's working fine for me on Ventura, same as 2.0.4

[tudor]

5 minutes ago, MikeTO said:

It's working fine for me on Ventura, same as 2.0.4

Have you actually tried selecting and moving nodes using alt-drag? On my computer it displays the lasso on screen, but it doesn't select anything.

[tudor]

Now it's doing something weird, it selects some nodes outside the selection area...

[Old Bruce]

Working fine here on Mac OS 11.7 with the latest betas (from today).

[tudor]

@Old Bruce could you open the attached file in the latest beta and try selecting some nodes with the lasso? Please let me know if it works correctly or not.

It's weird: on some files it works, on others it doesn't.

test.afdesign

[MikeTO]

14 minutes ago, tudor said:

@Old Bruce could you open the attached file in the latest beta and try selecting some nodes with the lasso? Please let me know if it works correctly or not.

It's weird: on some files it works, on others it doesn't.

I see the problem with your test file. It's not the shape, it's the position of the shape on the page so if you move the shapes to another position you'll get different results. I'm going to do some more testing.

[MikeTO]

Ah, it seems to be using the object's original coordinates when option-dragging to select notes. Start option-dragging around the nodes of any of the three copies of this simple path and they won't select until you drag over the nodes of the line in the upper left corner.

test.afdesign

[Xyz123]

Is the object you are trying to lasso select a duplicate of another shape? If so, you may be experiencing this same bug I found in 1730 (still present in 1732 for me).

 

[MikeTO]

40 minutes ago, Jocelyn said:

Is the object you are trying to lasso select a duplicate of another shape? If so, you may be experiencing this same bug I found in 1730 (still present in 1732 for me).

You're right, it's the same issue. But note that it's not duplicated shapes, it's moved shapes. Draw a path with two nodes, move it, and then trie to option+drag select the nodes. You need to drag around where the nodes originally were.

[Dazmondo77]

This has been driving me nuts off and on for a while, first noticing that I couldn't lasso shapes in certain documents in 2.0.4 through to latest beta

Good to see it's been highlighted so hopefully get a fix soon 

[dcarvalho84]

13 hours ago, MikeTO said:

You're right, it's the same issue. But note that it's not duplicated shapes, it's moved shapes. Draw a path with two nodes, move it, and then trie to option+drag select the nodes. You need to drag around where the nodes originally were.

Exactly, if you create a shape (i've used add to make a shape with a rectangle and some elipses) and try to select it with opt + drag it work just fine, but if you next move that shape and try to opt + drag it doesn't work.

[Sean P]

Thank you all! As Jocelyn said this is indeed the same issue - it is logged with development. 

[Old Bruce]

This gets my vote for ultra weird bug.

Moved or scaled will mess things up. A Boolean Add will fix them, but that isn't always possible.

[Dazmondo77]

2.1.0.1736 just to say it's not fixed yet 🙂

[Dazmondo77]

2.1.0.1742 just to say it's not fixed yet 🙂

[Dazmondo77]

YIPPEEEEEEE! this is now fixed in 2.1.0.1769 although I can't appear to find anything regarding Vector node lasso in the 2.1.0.1769 bug fix list

[Affinity Info Bot]

The issue "Lasso node selection fails on duplicated shapes" (REF: AFD-6510) has been fixed by the developers in internal build "2.1.0.1769".
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.