Ticket #3248 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Relocate/re-group threshold controls

Reported by: Owen Arnold Owned by: Owen Arnold
Priority: major Milestone: Iteration 30
Component: VATES Keywords:
Cc: zikovskyjl@… Blocked By:
Blocking: Tester: Michael Reuter

Description

Following #3235, should now follow the new advice and ensure that threshold ranges appear at a unique and separate location in the GUI to stop them being confused with other groups of controls.

Change History

comment:1 Changed 9 years ago by Owen Arnold

  • Component changed from Mantid to VATES

comment:2 Changed 9 years ago by Owen Arnold

  • Status changed from new to accepted

comment:3 Changed 9 years ago by Owen Arnold

(In [13043]) re #3248 #3319. Reorganise controls. For rebinning cutter, wire-up selections made of different Thresholding Strategies.

comment:4 Changed 9 years ago by Owen Arnold

(In [13048]) re #3248 Bring EventNexusReader up to the same level as the RebinningCutter filter in terms of use of ThresholdRange and associated controls.

comment:5 Changed 9 years ago by Owen Arnold

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

comment:6 Changed 9 years ago by Michael Reuter

  • Status changed from verify to verifying
  • Tester set to Michael Reuter

comment:7 Changed 9 years ago by Michael Reuter

  • Status changed from verifying to closed

This seems to be working correctly.

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4095

Note: See TracTickets for help on using tickets.