Certain instrument view python commands don't work

[Martyn Gigg]

While testing the commands at http://www.mantidproject.org/MantidPlot:_Viewing_the_Instrument_from_Python it became apparent that the setBinRange and selectComponent methods no longer worked.

The idea of these methods was that the values could be set before any rendering/integration had happened and when the window was shown it would be set to the values given in the scripts.

I.e. Setting the bin range should mean only calculating the integration once rather than calculaing the whole range on start up and then again when set.

[Russell Taylor]

A couple of other comments about accessing the instrument window from Python:

• If you enter a workspace name that doesn't exist into getInstrumentView, it silently fails (you get a NoneType back).
• Similarly, entering an incorrect path to a colormap silently does nothing.

[Andrei Savici]

This works for me:

Load('CNCS_7860_event.nxs','w')
instrument_view = getInstrumentView('w')
instrument_view.setColorMapMinValue(10.0)
instrument_view.setColorMapMaxValue(100.0)
instrument_view.show()

The default range is 0 to 175.

You might try in the python script:

if instrument_view==None:
   raise ValueError("workspace name not found or getInstrumentView failed")

[Russell Taylor]

The ticket title (which I've now changed) needed to be read in conjunction with the description! Only some commands were not working. In fact, 'setBinRange' does work now but 'selectComponent' still doesn't (for me).

[Nick Draper]

Moved to iteration 33 at iteration 32 code freeze

[Russell Taylor]

Since this release is big on python features, it would be good to get this working if anyone has time to look at it (I may do, but not today).....

[Nick Draper]

Martyn and Roman both have their hands full, could you pick this one up if you have the time

[Russell Taylor]

Add zooming to the named component when selecting a component

from python. Re #3784.

Changeset: 2a7e2ca238274dccd7e95910b19c5ef47e604838

[Russell Taylor]

Delay apparition of 'busy' cursor. Re #3784.

Changeset: 97c4a5f19b025a06c547fc417618754c68b6a6c0

[Russell Taylor]

Remove exposure of redundant method that didn't work anyway! Re #3784

Changeset: ea34dae9dc3d281f7871bf41bfceedebfc65b12f

[Russell Taylor]

All the exposed methods of InstrumentWindow work now, and are documented in the wiki.

What DOESN'T happen now is the instrument window starting out hidden on creation from python. I know how I would normally sort this out, but the floating windows business (#4282) seems to have made this a bit of a mess.

[Russell Taylor]

Instrument Window starts out hidden when created from python.

Unfortunately it flickers up briefly if the instrument window is docked (not the default), but I couldn't navigate my way through the floating windows minefield to stop that happening. Re #3784.

Changeset: 6687128eca5ad8b62a282efec6655852f774be82

[Alex Buts]

Tested on Win only.

Offending methods work fine. So all methods, mentioned on the web-page.

Floating windows behave strangely, for which a separate ticket #4541 has been risen.

[Russell Taylor]

Add zooming to the named component when selecting a component

from python. Re #3784.

Changeset: 2a7e2ca238274dccd7e95910b19c5ef47e604838

[Russell Taylor]

Delay apparition of 'busy' cursor. Re #3784.

Changeset: 97c4a5f19b025a06c547fc417618754c68b6a6c0

[Russell Taylor]

Remove exposure of redundant method that didn't work anyway! Re #3784

Changeset: ea34dae9dc3d281f7871bf41bfceedebfc65b12f

[Russell Taylor]

Instrument Window starts out hidden when created from python.

Unfortunately it flickers up briefly if the instrument window is docked (not the default), but I couldn't navigate my way through the floating windows minefield to stop that happening. Re #3784.

Changeset: 6687128eca5ad8b62a282efec6655852f774be82

[Stuart Campbell]

This ticket has been transferred to github issue ​4631