When a new atoms is passed from Python to the viewer, it will first check the uuid of the atoms and the uuid of the atoms in the viewer. Update the viewer and its plugins only when the uuids are different.
Here is the message chain, when user edit the atoms in the GUI.
1) users edit the atoms in the viewer (GUI)
--> 2) add a new uuid to the viewer.atoms, and dispatch a atomsUpdated event;
--> 3) An eventListener will trigger the update of the Python atoms;
---> 4) trigger the function to update the viewer. In this step, we will check if the new atoms and the atoms from the viewer are the same or not (by a unique uuid). In this case, the uuids will be the same, so there is no need to update the viewer.
When a new atoms is passed from Python to the viewer, it will first check the uuid of the atoms and the uuid of the atoms in the viewer. Update the viewer and its plugins only when the uuids are different.
Here is the message chain, when user edit the atoms in the GUI.
1) users edit the atoms in the viewer (GUI) --> 2) add a new uuid to the viewer.atoms, and dispatch a
atomsUpdatedevent; --> 3) An eventListener will trigger the update of the Python atoms; ---> 4) trigger the function to update the viewer. In this step, we will check if the new atoms and the atoms from the viewer are the same or not (by a unique uuid). In this case, the uuids will be the same, so there is no need to update the viewer.