Another new feature of the graph editor allows the user to delete more than one selected node in one step by using the editors menu Edit/Node/Delete Node.
In the new release V2.0.2, the ok is now sent in both cases again to guarantee compatibility with existing applications. So API programmers must expect the ok as the first answer from the API in any case.
To be consistent, daVinci V2.0.2 does not deselect the currently selected nodes when a new edge is selected. This means, answer node_selections_labels([]) is no longer sent in the first example shown above. The new semantic of API answer node_selections_labels([]) (with an empty list as argument) is that neither a node nor an edge is currently selected, i.e. everything is always deselected in this situation.
But this does not mean that for the application, the confirmation answer will directly follow after sending a command to the API. Answers for event notification may occur at any time, even if a command is not yet confirmed! The reason is that the event may have happened in the time interval after a command is send by the application, but before the command is received by daVinci. For daVinci, the event answer is then sent to the application before receiving the next command (which blocks sending of event answers). But for the application, the event answer is received from daVinci before getting the confirmation answer for the command.
Corollary: your daVinci application should expect to receive event answers at any time, even if a command, sent to the API, is not yet confirmed with the corresponding answer.