| Summary: | shift-selection of tree items is wrong, needs to remember a selection's anchor item | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Grant Gayed <grant_gayed> | ||||
| Component: | Client | Assignee: | libing wang <libingw> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | grant_gayed | ||||
| Version: | 4.0 | Flags: | grant_gayed:
review+
|
||||
| Target Milestone: | 4.0 RC2 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Grant Gayed
Just to clarify: All the non-shift single selection has to be the "shift selection anchor". Assume this flow: 1. Select a. 2. Hold Ctrl and select c. 3. Hold shift and select e. 4. Hold ctrl and select g. Then a,c,d,e,g are select. 5. hold shift and select e then g,f,e are selected. (In reply to libing wang from comment #1) I just tried this in Windows Explorer and the OS X Finder, and got slightly different results in them after your step 4: - Windows Explorer: c,d,e,g are selected - OS X Finder: a,c,d,e,g are selected I like the OS X behaviour better, but I guess either of these would be fine, they both make sense in slightly different ways. Created attachment 236302 [details]
Patch file
(In reply to Grant Gayed from comment #2) > (In reply to libing wang from comment #1) > > I just tried this in Windows Explorer and the OS X Finder, and got slightly > different results in them after your step 4: > - Windows Explorer: c,d,e,g are selected > - OS X Finder: a,c,d,e,g are selected > > I like the OS X behaviour better, but I guess either of these would be fine, > they both make sense in slightly different ways. I just implemented the windows explorer style. Shift selection should always clear the existing selection and create a new range of selection, unless we can cached the previously selections by CTRL key. (In reply to libing wang from comment #3) > Created attachment 236302 [details] > Patch file I think you can use Orion "apply patch" to review the changes. Thanks, grant. Pushed the fix with http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=8d43f32a741c2e2e3442b381f57a8209405c4318 |