search

mantidproject / mantid

Main repository for Mantid code
https://www.mantidproject.org
GNU General Public License v3.0
209 stars 122 forks source link

Sliceviewer - How to copy a value from the readout #29263

Closed NickDraper closed 3 years ago

NickDraper commented 4 years ago

image

Expected behavior

People may want to copy a value from the readout section when moving the cursor over the graph.

Actual behavior

There are two-layered problems:

  1. When you move the mouse up to the tool to the readout section, the selection moves, therefore the value you want changes, and blanks when you leave the image. OK, I've discovered you can kind of do this, but you have to:
    1. click on the track cursor checkbox to give that control focus
    2. Now pressing spacebar while moving over the graph will toggle track cursor allowing you to freeze the values However
    3. This is undocumented and not easy to do
    4. The side graphs still update when track cursor is disabled (this is confusing)
  2. the readout does not support copying (it is gray, is it disabled?)

suggested solution

  1. Add a keyboard shortcut for track cursor, and add it to the text of the control such as "Track Cursor (alt+c)", this needs to work whatever has the focus.
  2. Track cursor should also affect the tracking of the lineplots
  3. change the readout table to allow selection and copy to clipboard.
stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

stale[bot] commented 3 years ago

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.