Ticket #2123 (closed: duplicate)
Hide invalid workspaces
| Reported by: | Peter Peterson | Owned by: | Peter Peterson |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 30 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Nick Draper |
Description
If a workspace property defines a restriction on the workspace, then hide the invalid workspaces from the drop-down list. An example is the EventWorkspaceValidator should not allow crisp data to be in the list of workspaces.
Related to this is if a workspace is declared as a particular type (such as MatrixWorkspace) then the underlying gui code should try filtering by type with trying to dynamic cast the various workspaces to the appropriate types. In this example TableWorkspaces would not be shown.
Change History
comment:1 Changed 10 years ago by Nick Draper
- Status changed from new to assigned
- Owner set to Peter Peterson
comment:2 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 27 to Iteration 28
Bulk move of tickets at the end of iteration 27
comment:3 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 28 to Iteration 29
Bulk move of tickets at the end of iteration 28
comment:4 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 29 to Iteration 30
Accepted and assigned tickets moved at iteration 29 code freeze
comment:5 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:7 Changed 9 years ago by Peter Peterson
- Status changed from accepted to verify
- Resolution set to duplicate
Nick just announced during the scientific steering committee meeting that this is already done.
comment:8 Changed 9 years ago by Nick Draper
- Status changed from verify to verifying
- Tester set to Nick Draper
comment:9 Changed 9 years ago by Nick Draper
- Status changed from verifying to closed
True, this was changed for the last iteration
comment:12 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 2970
The question here is how long it takes some of the validators to run. If you have a case of 30 workspaces, and the validator is throrough and takes 0.1 seconds then you get a delay of 3 seconds in displaying the list.
So I think we just need to check how long the validators can take before we go implementing this one. I'm particularly concerned about the Ragged Workspace validator as I don't know how much of the dataset it checks.