Ticket #3694 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

plot spectrum dialoge in mantid plot workspace bar

Reported by: Jon Taylor Owned by: Peter Parker
Priority: critical Milestone: Release 2.0
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Karl Palmen

Description

Right clicking on a workspace on the workspaces side bar has the option of "plotSpectrum" this then creates a dialogue that actually asks the user for a workspace index, rather than spectrum number.

Change History

comment:1 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:2 Changed 9 years ago by Nick Draper

Nick to discuss with Jon on naming options

comment:3 Changed 9 years ago by Nick Draper

  • Priority changed from major to critical
  • Owner set to Anyone
  • Status changed from new to assigned

Adjust the pop up box to be more clever.

  1. If the workspace has a spectrum index, then also present a spectrum number box, with a small label showing the acceptable values
  2. The workspace index box should always be present, but also add a small label listing the max and min values (eg. acceptable values 0-251)

comment:4 Changed 9 years ago by Nick Draper

  • Owner changed from Anyone to Peter Parker

comment:5 Changed 9 years ago by Peter Parker

  • Status changed from assigned to accepted

comment:6 Changed 9 years ago by Peter Parker

In [15292]:

Implements functionality as per Nicks comment above, except that we now also support the user being able to specify a range (or ranges) of spectra ID / ws indices to plot, e.g. "2, 5-7" will plot 2, 5, 6 and 7. Refs #3694

comment:7 Changed 9 years ago by Peter Parker

In [15294]:

Fixed issues after merging, and also changed all occurences of "..>>.." to "..> >.." where appropriate to avoid non-VS2010 compiler errors. Refs #3694

comment:8 Changed 9 years ago by Peter Parker

In [15295]:

Changed few more occurences of "..>>.." to "..> >.." where appropriate to avoid non-VS2010 compiler errors. Refs #3694

comment:9 Changed 9 years ago by Peter Parker

In [15296]:

Unsure about how to fix some of the errors/warning at the moment. Will revert to make way for move to git and work on finding a solution in the meantime. Refs #3694

comment:10 Changed 9 years ago by Peter Parker

In [15333]:

Hopefully this fixes all warnings/errors on non Windows builds ... - Refs #3694

comment:11 Changed 9 years ago by Peter Parker

In [15334]:

Another try ... - Refs #3694

comment:12 Changed 9 years ago by Peter Parker

  • Status changed from accepted to verify
  • Resolution set to fixed

comment:13 Changed 9 years ago by Mathieu Doucet

In [15341]:

Fix warning. Re #3694

comment:14 Changed 9 years ago by Karl Palmen

  • Status changed from verify to verifying
  • Tester set to Karl Palmen

comment:15 Changed 9 years ago by Karl Palmen

  • Status changed from verifying to closed

comment:16 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 4541

Note: See TracTickets for help on using tickets.