Skip to content
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

Column types on a MantidTable #5565

Closed
mantid-builder opened this issue Feb 1, 2012 · 1 comment
Closed

Column types on a MantidTable #5565

mantid-builder opened this issue Feb 1, 2012 · 1 comment
Assignees

Comments

@mantid-builder
Copy link
Collaborator

This issue was originally TRAC 4718

Original Reporter: Russell Taylor

A follow on from http://trac.mantidproject.org/mantid/ticket/4634.

By default, a qtiplot table is created with the first column labelled as [X] and subsequent columns as [Y]. Probably for a MantidTable we should just set all columns to 'no type' unless the TableWorkspace contains a specific setting (or is of a specific type such as text). In this case, setting it from the 'top' (e.g. GenericFit) should be unnecessary.

Other points:

  • At the moment, the 'plottype' within the workspace is lost on saving and loading the project. I.e. display the table workspace from a fit again and the column is back to [X] not [L].
  • Overloading the Table::setColPlotDesignation(int, unsigned int) method with one that takes (int, int) is odd and unnecessary.
@mantid-builder
Copy link
Collaborator Author

@NickDraper (2012-02-14T11:12:39):
I disagree that everything should be notype, but you should be able to change the column type when displaying the tableworkspace.


@NickDraper (2012-04-30T14:12:58):
Moved at end of release 2.1


@NickDraper (2012-08-10T12:43:39):
Moved at the end of release 2.2


@NickDraper (2012-10-28T11:38:50):
Moved to milestone 2.4


@NickDraper (2013-01-28T09:23:02):
Moved at the code freeze for release 2.4


@NickDraper (2013-04-29T09:49:39):
Moved to r2.6 at the end of r2.5


@NickDraper (2013-07-26T13:54:59):
Moved to backlog at the code freeze for R2.6


@NickDraper (2014-02-14T11:04:56):
Bulk move to assigned at the introduction of the triage step

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants