by m.Th. (Posted Tue Feb 14, 2017 10:32 am)
From my little experience (we have a suite of programs in which we have used from many years extensively the multi-select tree of keywords for searching/filtering) the best thing for the users is:
When one clicks on an item toggle the selection of the said item ONLY.
Provide as a right-click menu option the followings:
- Select all children
- Deselect all children
- Toggle all children
The above are quite powerful and usually can be done with the same piece of code (same iterator) - the only change needed is, of course, the actual action which is oCrtNode.Checked = True - or - oCrtNode.Checked = False - or - oCrtNode.Checked = not oCrtNode.Checked .
Something like this.
This is a distinctive feature from Lr which can be a very powerful one, mitigating the need of freezing the tree structure by saving in the file/sidecar the entire path of keywords - for example : Europe | France | Paris. With the feature above we can be much more flexible and faster.
Read Main Topic
From my little experience (we have a suite of programs in which we have used from many years extensively the multi-select tree of keywords for searching/filtering) the best thing for the users is:
When one clicks on an item toggle the selection of the said item ONLY.
Provide as a right-click menu option the followings:
- Select all children
- Deselect all children
- Toggle all children
The above are quite powerful and usually can be done with the same piece of code (same iterator) - the only change needed is, of course, the actual action which is oCrtNode.Checked = True - or - oCrtNode.Checked = False - or - oCrtNode.Checked = not oCrtNode.Checked .
Something like this.
This is a distinctive feature from Lr which can be a very powerful one, mitigating the need of freezing the tree structure by saving in the file/sidecar the entire path of keywords - for example : Europe | France | Paris. With the feature above we can be much more flexible and faster.
Read Main Topic