Fixed issues in Global Search UI where if a child node was selected and the user selected the parent of that node, the UI was deselecting the child node but selecting all other "unselected" children. The same thing happened when you "deselected" the parent where any deselected child would then become selected.
Additionally, the way that the search list is populated is by using the node tag property. This worked fine until we added the capability of selecting a parent node. By design the parent did not have a tag since it was previously not selectable. Now that it is selectable I needed to modify the code to account for that. Previously the only node that did not have a tag is the "WORD Section" node. By adding an additional check on lines 2563 and 2587 we are able to determine if we are dealing with a WORD Section or a parent node without a tag value.
Lastly, since there is currently no code for handling the selection of child nodes programmatically, we have to set 2 properties and call the advTreeStepTypes_AfterCheck method again to process those child nodes.
Fixed issues in Global Search UI where if a child node was selected and the user selected the parent of that node, the UI was deselecting the child node but selecting all other "unselected" children. The same thing happened when you "deselected" the parent where any deselected child would then become selected.
Additionally, the way that the search list is populated is by using the node tag property. This worked fine until we added the capability of selecting a parent node. By design the parent did not have a tag since it was previously not selectable. Now that it is selectable I needed to modify the code to account for that. Previously the only node that did not have a tag is the "WORD Section" node. By adding an additional check on lines 2563 and 2587 we are able to determine if we are dealing with a WORD Section or a parent node without a tag value.
Lastly, since there is currently no code for handling the selection of child nodes programmatically, we have to set 2 properties and call the **advTreeStepTypes_AfterCheck** method again to process those child nodes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixed issues in Global Search UI where if a child node was selected and the user selected the parent of that node, the UI was deselecting the child node but selecting all other "unselected" children. The same thing happened when you "deselected" the parent where any deselected child would then become selected.
Additionally, the way that the search list is populated is by using the node tag property. This worked fine until we added the capability of selecting a parent node. By design the parent did not have a tag since it was previously not selectable. Now that it is selectable I needed to modify the code to account for that. Previously the only node that did not have a tag is the "WORD Section" node. By adding an additional check on lines 2563 and 2587 we are able to determine if we are dealing with a WORD Section or a parent node without a tag value.
Lastly, since there is currently no code for handling the selection of child nodes programmatically, we have to set 2 properties and call the advTreeStepTypes_AfterCheck method again to process those child nodes.