VSE: Select more/less functionality breaks on certain conditions #89913

New Issue

David Salvo · 2021-07-17T10:14:59+02:00

David Salvo commented

2021-07-17 10:14:59 +02:00

System Information
Operating system: Linux Mint 20
Graphics card: NVIDIA G92 [GeForce 9800 GT]

Blender Version
Broken: 2.93.1 / 2.92.0
Worked: Unsure

The functions sequencer.select_more and sequencer.select_less get stuck when the newly selected strip reaches an edge, or when number of selected strips becomes zero.

Exact steps for others to reproduce the error
blender-bug__select-more-less.mp4

The attached video shows the functions [select_more]/[select_less] will break when the following conditions are met:

 a) Any strip chain selection reaches the edge of the row of strips with [select_more]
    i) either when it starts from an edge and reaches the other edge
    ii) or when it starts in the middle and expands from both sides, the side of whichever edge is met will get stuck
 b) Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more]

I think it's unlikely this is intended behaviour?

Sorry I didn't get visual keypresses set up for the video, but I'm just using CTL- [x] and CTL- [x] on num pad as per default.

David

**System Information** Operating system: Linux Mint 20 Graphics card: NVIDIA G92 [GeForce 9800 GT] **Blender Version** Broken: 2.93.1 / 2.92.0 Worked: Unsure The functions sequencer.select_more and sequencer.select_less get stuck when the newly selected strip reaches an edge, or when number of selected strips becomes zero. **Exact steps for others to reproduce the error** [blender-bug__select-more-less.mp4](https://archive.blender.org/developer/F10226415/blender-bug__select-more-less.mp4) The attached video shows the functions [select_more]/[select_less] will break when the following conditions are met: ``` a) Any strip chain selection reaches the edge of the row of strips with [select_more] i) either when it starts from an edge and reaches the other edge ii) or when it starts in the middle and expands from both sides, the side of whichever edge is met will get stuck b) Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more] ``` I think it's unlikely this is intended behaviour? Sorry I didn't get visual keypresses set up for the video, but I'm just using CTL- [x] and CTL- [x] on num pad as per default. David

David Salvo commented

2021-07-17 10:14:59 +02:00

Added subscriber: @slinkeepie

Pratik Borhade commented

2021-07-19 02:37:30 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-07-19 02:47:59 +02:00

Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more]

At least a strip needs to be selected to expand or reduce the selected elements. So I don't think this is a bug or so.

stuck when the newly selected strip reaches an edge,

Don't think this is expected. Also: Selection works same in edit mode when all edge/face/verts are selected.

> Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more] At least a strip needs to be selected to expand or reduce the selected elements. So I don't think this is a bug or so. >stuck when the newly selected strip reaches an edge, Don't think this is expected. Also: Selection works same in edit mode when all edge/face/verts are selected.

David Salvo commented

2021-07-19 09:22:51 +02:00

In #89913#1192815, @PratikPB2123 wrote:

Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more]

At least a strip needs to be selected to expand or reduce the selected elements. So I don't think this is a bug or so.

You're right, probably not technically a bug... but with regards to these functions, it seems counterintuitive.

stuck when the newly selected strip reaches an edge,

Don't think this is expected. Also: Selection works same in edit mode when all edge/face/verts are selected.

Glad you agree with that :)

As for behaviour on edge reach by dual-expanded selection, that has a bit of room for interpretation on what the most logical behaviour is... probably whatever side gets increased past the edge (one activation past reaching the edge) should stay stuck, turning it into a singly expanded selection at that point. But it's a fairly niche usage of the function to be honest. It would be more helpful to have a [select_more_to_left] and [select_more_to_right] function split...

Thanks so much for the quick response!
David

> In #89913#1192815, @PratikPB2123 wrote: >> Any strip selection becomes empty with [select_less], i.e. the selection won't grow again with [select_more] > At least a strip needs to be selected to expand or reduce the selected elements. So I don't think this is a bug or so. You're right, probably not technically a bug... but with regards to these functions, it seems counterintuitive. > >>stuck when the newly selected strip reaches an edge, > Don't think this is expected. Also: Selection works same in edit mode when all edge/face/verts are selected. Glad you agree with that :) As for behaviour on edge reach by *dual-expanded* selection, that has a bit of room for interpretation on what the most logical behaviour is... probably whatever side gets increased *past* the edge (one activation past reaching the edge) should stay stuck, turning it into a singly expanded selection at that point. But it's a fairly niche usage of the function to be honest. It would be more helpful to have a [select_more_to_left] and [select_more_to_right] function split... Thanks so much for the quick response! David

Pratik Borhade commented

2021-07-19 10:30:51 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Pratik Borhade commented

2021-07-19 10:30:51 +02:00

Added subscriber: @iss

Pratik Borhade commented

2021-07-19 10:30:51 +02:00

@iss can you please check the issue? Select less presently does not work when all strips are selected. Is this a known issue or an intentional behavior?

@iss can you please check the issue? `Select less` presently does not work when all strips are selected. Is this a known issue or an intentional behavior?

Richard Antalik commented

2021-07-20 04:26:31 +02:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Richard Antalik commented

2021-07-20 04:26:31 +02:00

In VSE select less fails, because strip doesn't have any unselected neighbors, which looks like bug. It really should shrink selection from edges.
Issue, that select less can end up with no selection is intended behavior. Not sure if it's useful in VSE. If this is issue for your workflow, please explain bit more in detail.

The behavior seems to be the same in 3D edit mode with vertices. Perhaps it's same issue.

In VSE select less fails, because strip doesn't have any unselected neighbors, which looks like bug. It really should shrink selection from edges. Issue, that select less can end up with no selection is intended behavior. Not sure if it's useful in VSE. If this is issue for your workflow, please explain bit more in detail. The behavior seems to be the same in 3D edit mode with vertices. Perhaps it's same issue.

David Salvo commented

2021-07-20 16:23:44 +02:00

Thanks Richard...
There's no problem with ending up with zero selection (seems expected). As for starting up from zero selection at the point last selected, it would require something context sensitive that probably isn't worth the work for a niche case of a fairly niche operation I guess. It's just something I noticed that seemed not quite right to my very stringent brain when customizing my hotkeys and testing what all the functions do hehe. Not sure if it would be useful in other modes since I mainly edit...

Agreed that full selection should definitely shrink down when select_less is used.

David

Thanks Richard... There's no problem with ending up with zero selection (seems expected). As for starting up from zero selection at the point last selected, it would require something context sensitive that probably isn't worth the work for a niche case of a fairly niche operation I guess. It's just something I noticed that seemed not quite right to my very stringent brain when customizing my hotkeys and testing what all the functions do hehe. Not sure if it would be useful in other modes since I mainly edit... Agreed that full selection should definitely shrink down when select_less is used. David

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE: Select more/less functionality breaks on certain conditions #89913