Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent selection methods #956

Open
nathaneltitane opened this issue Nov 5, 2024 · 0 comments
Open

Inconsistent selection methods #956

nathaneltitane opened this issue Nov 5, 2024 · 0 comments
Labels

Comments

@nathaneltitane
Copy link

Describe the bug
timeline widget vs model space has nconsistent selection methods (cannot double click on timeline to 'red'select parts'

this issue is also akin to a problem with the introduction of the new version of the parts property widget where an apparent 'bug' was fixed where leocad now expects a double click for any selections to take effect on a multiple instance level (part or color)

this newly fixed behavior is incompatible with the timeline and the selection filters (part/color/part+color) where the whole point of these was to accelerate selection and modification of parts or groups of parts - the current result is confusing as the last selected item (model space) remains blue and is then the ONLY item to be modified.

To Reproduce
Steps to reproduce the behavior:
open model
select any component on timeline (double click)
component remains blue

effectively: cannot do a double click selection on the timeline of items and must resort to navigation within the 3d model (cumbersome and error prone)

Expected behavior
double clicking items on timeline should result in 'red' selected items.
clicking multiple items (in general, and regardless of last selcted item being blue should make filters and parts properties widget alter ALL selected parts/items)

Screenshots
image

Version (please complete the following information):
debian 12 x64 latest

Crash information:
Some versions of LeoCAD will show a message that they saved a minidump file when they crash, if you see this message please attach the file.

Additional context

ref.: #931

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant