Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
There are several issues here:
:: Bursts may have taken a long time for calculation. That should be indicated somehow.
:: A single burst entry in the History list may stand for a parameter space exploration. That should be indicated somehow.
If the user clicks on the "Delete" button for an existing burst, there should be modal confirmation dialog offering a cancel action. Maybe this dialog could only show up for bursts representing a considerable amount of data or processing time (or being just processed in background).