| Summary: | Mini-nav does not reveal resource always since tree parent is empty | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Silenio Quarti <Silenio_Quarti> | ||||
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | simon_kaegi | ||||
| Version: | 4.0 | Flags: | simon_kaegi:
review+
|
||||
| Target Milestone: | 4.0 RC3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Silenio Quarti
I tracked this problem down and it happens because we are creating the mini-nav explorer twice. The first instance of the explorer is actually destroyed, but there is a outstanding request to the server to load the parent children. When this request finishes, the tree is rendered even though the widget (treetable) has already been destroyed. Created attachment 237031 [details]
fix
This patch has been pushed to the R4.0RC3_maintenance branch: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?h=R4.0RC3_maintenance&id=85bb87dbdff696b5b6c33e75bbc9b2382002c0b1 Fixed in 4.0 |