Dynamic property validation

[Martyn Gigg]

At present, the NormaliseToMonitor algorithm requires that you enter the spectrum number relating to the monitor you wish to use. It would be much nicer, particularly when using MantidPlot, to give the name of the monitor instead. But this isn't known until the input workspace has been set, so we would need to find a way in which the setting of the input workspace fired an event that the monitor property could catch and update itself.

Span off from #262

[Nick Draper]

After thinking of a solution it should be discussed via mantid.developers@… before implementation

[Alex Buts]

This feature will be extremely useful for multidimensional algorithm creation, as the dimensions, available for MD algorithms depend on user input and the log values, present in a workspace. Namely: 1) Number of dimension properties is defined by the user's input into Num_dimensions field

2) The dimension properties are the lists of strings, partially derived from the log names present in the input workspace

3) Two different dimension property can not provide the same value from the list (this can be of course checked during the algorithm execution but will be nicer on properties)

[Alex Buts]

In [15304]:

refs #3925 first and wrong attempt to use/create dynamic properties to generate ConvertToN-dimensions algorithm.
Apparently, this ticket is bind with ticket refs#3763

[Alex Buts]

refs #3925, refs #3763 initial attempt to implement signaling validators

Changeset: d07ca5327f62dd36639076e6400f50abcfd98fab

[Alex Buts]

refs #3763 fixing Unix error

Changeset: 7671abb942a4c9e194f56c18658dbdf9f86eb0ae

[Alex Buts]

refs #3763 fixing unix error

Changeset: c49fb86af29874cef246796b00e0d35f7f669b49

[Alex Buts]

refs #3763 added allowedValue function to CompositeValidator.cpp

Changeset: 6b9f6e45817ec5b6adb9a122d9a65f909eb77811

[Alex Buts]

refs #3925, refs #3763 initial attempt to implement signaling validators

Changeset: d07ca5327f62dd36639076e6400f50abcfd98fab

[Alex Buts]

refs #3763 fixing Unix error

Changeset: 7671abb942a4c9e194f56c18658dbdf9f86eb0ae

[Alex Buts]

refs #3763 fixing unix error

Changeset: c49fb86af29874cef246796b00e0d35f7f669b49

[Alex Buts]

refs #3763 fixing warning and couple of comments

Changeset: 25e85e1515dfcbac705e78364c0bb1a9b3b99719

[Alex Buts]

refs #3763 fixing warning and couple of comments

Changeset: 3d6ff6f66464f1b9cdb2775fc596ebf3a9362303

[Alex Buts]

refs #3763 Fixing Unix build

Changeset: eb9c8b25b8e171dec2b6c452ce321079654689eb

[Alex Buts]

refs #3763 Fixing Unix warning

(to see where the error actually come from)

Changeset: 3a92482c70994464c990e6a91f59fa51ec137806

[Alex Buts]

refs #3763 Attempt to fix unix build

Changeset: 410166af8f20a95456dacf1e5c43ca9aeca3cb63

[Alex Buts]

refs #3763 Warnings&comments

Changeset: 991a84c7b83010e00eb4674edcf2e07b79576fb2

[Alex Buts]

refs #3763 Crude implementation of Dynamic properties.

Will not work properly form framework when property modifier change validator in such a way, that old value of the dependent property is incorrect. Substantial changes needed to rectify that and to avoid such situation, so currently has to be dealt with by user.

It would be also beneficial to implement proper notification mechanism, which would inform the property about the changes in the properties it depends on, as current implementation can potentially have substantial overhead, which user should be really carefull about.

Changeset: c8d3a5aaaae6a7f69d0522bcfec333b870dc23f3

[Alex Buts]

refs #3763 Fixing Unix build

Changeset: eb9c8b25b8e171dec2b6c452ce321079654689eb

[Alex Buts]

refs #3763 Fixing Unix warning

(to see where the error actually come from)

Changeset: 3a92482c70994464c990e6a91f59fa51ec137806

[Alex Buts]

refs #3763 Attempt to fix unix build

Changeset: 410166af8f20a95456dacf1e5c43ca9aeca3cb63

[Alex Buts]

refs #3763 Warnings&comments

Changeset: 991a84c7b83010e00eb4674edcf2e07b79576fb2

[Alex Buts]

refs #3763 Crude implementation of Dynamic properties.

Will not work properly form framework when property modifier change validator in such a way, that old value of the dependent property is incorrect. Substantial changes needed to rectify that and to avoid such situation, so currently has to be dealt with by user.

It would be also beneficial to implement proper notification mechanism, which would inform the property about the changes in the properties it depends on, as current implementation can potentially have substantial overhead, which user should be really carefull about.

Changeset: c8d3a5aaaae6a7f69d0522bcfec333b870dc23f3

[Alex Buts]

refs #3763 ValidatorSignalChange.h removed

Changeset: edbe935d3fe0150d755748beaa31c5d67ff0922f

[Nick Draper]

Moved to iteration 33 at iteration 32 code freeze

[Nick Draper]

Moved at end of release 2.1

[Nick Draper]

http://www.mantidproject.org/Release_Notes_2_2_Full_List

[Nick Draper]

Moved to milestone 2.4

[Nick Draper]

Moved at the code freeze for release 2.4

[Nick Draper]

Moved to r2.6 at the end of r2.5

[Nick Draper]

Moved to the Backlog after the code freeze for R2.6

[Nick Draper]

bulk move to assigned at the into of the triage step

[Stuart Campbell]

This ticket has been transferred to github issue ​4610