| Summary: | Minor selection improvement | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | manuelchaves |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | minor | CC: | dolphin-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Ctrl and shift actions | ||
Created attachment 171398 [details] Ctrl and shift actions This is a small detail that I think might be missing. If you see the attached gif, you'll see in the first action how ctrl pick + shift range pick works as expected. But in the second action I toggle off the ctrl-picked item, yet the shift range selection still happens at that point. If the item is toggled off it shouldn't count as a starting point for a selection, I think. What I did in my own implementation (in another application) was keep a date of selection on every selected item. And I use the most recently selected item as the starting point for range selections. When an item is deselected the date is set to 0. This is not critical but I thought I'd just share it just in case.