| Summary: | [Operations] Operations spinning wheel shown when it should not | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Szymon Brandys <Szymon.Brandys> | ||||
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | malgorzata.tomczyk, simon_kaegi | ||||
| Version: | 1.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Szymon Brandys
Created attachment 224218 [details]
Screenshot
The navigator page shows operations triggered by another page.
Generally when Bug 395260 is resolved the background operations should not be shown under the spinning weal. However I talked to Szymon and we both agree that in some situations we would like to see on the current page operations that are running in background. We talked that we could use a similar idea we used in related pages. If operations would "know" the resource on which it's performed we could use this knowledge to list operations related to the current resource on the page. For instance when we open a folder in navigator that has GitCloneLocation we could use the GitCloneLocation to check if there are any operations running on this git clone. This way in the navigator we could display information that Git Clone on the current folder is now running. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |