You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a node has children (relative positions), and it is moved, the positions of the children are not immediately recalculated. This gives a situation where the imagemap doesn't update, but the image itself does (because it involves reloading the config). The move takes fully place as expected after any other change (or 'do nothing').
Immediately after a node move, relative positions should be recalculated. There is no convenient facility to do this currently.
Temporary fix: just press "do nothing" or edit something else.
The text was updated successfully, but these errors were encountered:
I am aware of the bug in #95, I experienced many times in the past. to get around it I usually reload a config in editor by open a new config file:). Fix for it would be nice!
When a node has children (relative positions), and it is moved, the positions of the children are not immediately recalculated. This gives a situation where the imagemap doesn't update, but the image itself does (because it involves reloading the config). The move takes fully place as expected after any other change (or 'do nothing').
Immediately after a node move, relative positions should be recalculated. There is no convenient facility to do this currently.
Temporary fix: just press "do nothing" or edit something else.
The text was updated successfully, but these errors were encountered: