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.

Sign up for GitHub

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

Jump to bottom

InstrumentSelector should not change the default instrument #223

Merged
merged 3 commits into from Feb 17, 2015
Merged

InstrumentSelector should not change the default instrument #223

merged 3 commits into from Feb 17, 2015

Conversation

DanNixon
Copy link
Member

Ticket #11049.

To test:

  • Verify that changes to the default instrument on configuration UI and first time setup are persisted as expected.
  • Verify that the MWRunFile widgets on Direct Convert to Energy and Muon Analysis attempt to load the correct file for the available instruments on the instrument selector (should be prefixed with instrument selected in UI, can be seen with log level set to debug)

@DanNixon DanNixon added the GUI label Feb 16, 2015
@DanNixon DanNixon added this to the Release 3.4 milestone Feb 16, 2015
@DanNixon
Copy link
Member Author

Jenkins, retest this please.

1 similar comment
@DanNixon
Copy link
Member Author

Jenkins, retest this please.

@eXeC64 eXeC64 self-assigned this Feb 17, 2015
eXeC64 added a commit that referenced this pull request Feb 17, 2015
@eXeC64
Merge pull request #223 from mantidproject/feature/11049_instrumentse…
0dbbd4e 
…lector_not_change_default_instrument

InstrumentSelector should not change the default instrument
@eXeC64 eXeC64 merged commit 0dbbd4e into master Feb 17, 2015
@eXeC64 eXeC64 deleted the feature/11049_instrumentselector_not_change_default_instrument branch February 17, 2015 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@eXeC64 eXeC64

Labels
None yet
Projects
None yet
Milestone
Release 3.4
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@DanNixon @eXeC64