Fix child-creation-needs-value nodes.
We only want to do a delete/create cycle if the node actually changed. Fixes BMessageValueNode.
This commit is contained in:
@@ -955,15 +955,15 @@ VariablesView::VariableTableModel::ValueNodeChanged(ValueNodeChild* nodeChild,
|
|||||||
return;
|
return;
|
||||||
|
|
||||||
AutoLocker<ValueNodeContainer> containerLocker(fContainer);
|
AutoLocker<ValueNodeContainer> containerLocker(fContainer);
|
||||||
|
|
||||||
ModelNode* modelNode = fNodeTable.Lookup(nodeChild);
|
ModelNode* modelNode = fNodeTable.Lookup(nodeChild);
|
||||||
if (modelNode == NULL)
|
if (modelNode == NULL)
|
||||||
return;
|
return;
|
||||||
|
|
||||||
if (oldNode != NULL)
|
if (oldNode != NULL) {
|
||||||
ValueNodeChildrenDeleted(oldNode);
|
ValueNodeChildrenDeleted(oldNode);
|
||||||
ValueNodeChildrenCreated(newNode);
|
ValueNodeChildrenCreated(newNode);
|
||||||
fContainerListener->ModelNodeValueRequested(modelNode);
|
fContainerListener->ModelNodeValueRequested(modelNode);
|
||||||
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user