You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If there is an active "Search Parts" query, "Parts" list scrolls to the bottom every time swithching between categories.
Rarely, in same of the cases it acts as usual and scrolls to top, in some other it scrolls to the middle of the list.
To Reproduce
Steps to reproduce the behavior:
Add any word to "Search Parts" query on "Parts" list widget;
Switch between categories;
Try different queries (numeric, words, mixed)
Expected behavior
If there is an active "Search Parts" query, "Parts" list should not scrolls to the bottom, and when switching categories it should be alwaysscrolls to the top of the list.
And allparts not matching query should be hiddent if there is active "Search Parts" query.
Screenshots
Screencast video
leocad-parts-list-scroll-with-search-parts.webm
Version (please complete the following information):
OS: Debian 12
LeoCAD Version: continuous (AppImage)
Crash information:
None
Additional context
None
The text was updated successfully, but these errors were encountered:
Describe the bug
If there is an active "Search Parts" query, "Parts" list scrolls to the bottom every time swithching between categories.
Rarely, in same of the cases it acts as usual and scrolls to top, in some other it scrolls to the middle of the list.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If there is an active "Search Parts" query, "Parts" list should not scrolls to the bottom, and when switching categories it should be alwaysscrolls to the top of the list.
And allparts not matching query should be hiddent if there is active "Search Parts" query.
Screenshots
Screencast video
leocad-parts-list-scroll-with-search-parts.webm
Version (please complete the following information):
Crash information:
None
Additional context
None
The text was updated successfully, but these errors were encountered: