| Summary: | Project renaming and tree refreshing problem (1GFQQ5V) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Lynne Kues <lynne_kues> |
| Component: | UI | Assignee: | Kevin Haaland <Kevin_Haaland> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | critical | ||
| Priority: | P4 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Lynne Kues
moved to 'active' PRODUCT VERSION: 125 scenario below works in the latest and the tree is in sync I reran the scenario in the PR and the tree is no longer out of sync. However, the collapse behavior is still inconsistent when you rename. Why does the tree get collapsed on the first rename operation, but not on the second rename operation? This is inconsistent if not a bug. Also, it would be most user friendly to always leave the tree in its expanded state when a rename operation occurs. Tested all of this in 20011107. Agreed the collapse behaviour is not consistent. This is a JFace problem 3840. Moving to Platform UI. |