-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for (x,y,e) readback from graph on mouse over (Trac #185) #333
Comments
Trac update at |
Trac update at Clicking anywhere on the graph currently puts the coordinates in the status bar area. It would probably be better to have this functionality such that information is printed in the graph window somewhere. |
Trac update at |
Trac update at |
Trac update at |
Trac update at |
Trac update at |
Trac update at
More importantly for 2D plots the intensity is NOT accessible since x and y both are now co-ordinate values.
to:
|
Trac update at
Closing this ticket as the feature requested does in fact exist. getting x,y, AND z in the 2D plots should be a separate ticket but probably should wait for the new GUI
|
"When we plot a graph, it is possible with the cursor to point on a curve to have access to the (x,y) coordinate of a point? I think it is very useful to have a rapid information of the intensity level at a q value."
Arnauld Poulesquen
CEA Marcoule
DEN/DTCD/SPDE/L2ED
Laboratoire de Chimie des Fluides Complexes et d'Irradiation
Bât. 37 - BP 17171
F - 30 207 Bagnols sur Cèze
FRANCE
Tél. : +33 (0)4.66.79.18.01
Fax : +33 (0)4.66.39.78.71
Response by SMK for !SasView Developers, 14/05/13:
"As far as I know this is not possible at the moment, but I agree it would be a nice feature. The best !SasView can offer is if you right-click on ANY data point and move down the context menu to the name of the data set you are interested in, then follow the chevron to !DataInfo. A window will pop-up and if you scroll down you will get a listing of all the (x,y,e) values for that data set. I will ticket the feature you ask for (but at this juncture I do not know how feasible it may be or how quickly it will be implemented)."
Migrated from http://trac.sasview.org/ticket/185
The text was updated successfully, but these errors were encountered: