To avoid this problem, you can override the update by undefined in nodeDefinition. A: Since the extendedTypeName is assigned, and the update is not implemented in extendedTypeName, the update of the extended node type will be called when updating the node/edge, whose logic might be different from the draw or drawShape defined by yourself.e.g., some shapes are not updated as expected, and some text shapes show up. Q: when the custom node/edge is updated, the re-draw logic is not the same as draw or drawShape function defined in nodeDefinition.Due to this mechanism, a question is often fed back: Noted that if the extendedTypeName is assigned, the required functions such as draw, update, and setState will extend from extendedTypeName unless they are rewritten in nodeDefinition. When the extendedTypeName is assigned, the functions which are not rewritten will extend from the type with name extendedTypeName. The required options can be found at Custom Mechanism API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |