Ticket #3360 (closed: worksforme)
Interacting box off by default
Reported by: | Owen Arnold | Owned by: | Michael Reuter |
---|---|---|---|
Priority: | major | Milestone: | Release 2.6 |
Component: | GUI | Keywords: | |
Cc: | russell.ewings@… | Blocked By: | |
Blocking: | Tester: | Owen Arnold |
Description (last modified by Nick Draper) (diff)
Users are finding confusing that they end up interacting with the various interaction tools, when the actually just want to pan around their visualisation data.
Having the interacting tools hidden/off by default would fix this. Can we do this in PV without modifying framework code?
Change History
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:3 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:4 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:9 Changed 7 years ago by Michael Reuter
- Status changed from accepted to verify
- Resolution set to worksforme
I think with the new views, this is no longer an issue, but can someone please have a look to see if the intent of this ticket has been satisfied with the 2.5 release?
comment:10 Changed 7 years ago by Owen Arnold
- Status changed from verify to verifying
- Tester set to Owen Arnold
comment:11 Changed 7 years ago by Owen Arnold
- Status changed from verifying to closed
Agree with Michael here. New custom views are individually geared to a way of working with neutron data, so this is not an issue.
comment:12 Changed 7 years ago by Nick Draper
- Component changed from VATES to User Interface
- Description modified (diff)
comment:13 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 4207
Bulk move of tickets to iteration 31 at the iteration 30 code freeze