| Re: [sapphire-dev] tool palette "actions" |
Good point. I’ll make sure the “palette drop” does use the Sapphire add action on my side. Shenxue From: Konstantin Komissarchik There might be enough in place already for Greg to accomplish what he is after. Both palette drop and add via the context menu, should be invoking the add action. Greg should be able to (in sdef) to filter our system-provided add action handlers and replace them with his own. The only piece that might be necessary (I haven’t looked) is to expose the system-provided add action handler class as API so that it can be subclassed to customize its behavior instead of starting from scratch. Thanks, - Konstantin From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Shenxue Zhou Hi Greg, We could add support for a “pre-action” right before the model element corresponding to the node is created. Could you open an enhancement request? Thanks, Shenxue From: Greg Amerson [mailto:gregory.amerson@xxxxxxxxxxx] Is there a way right now to execute an action after a user has dropped a palette action but before the diagram model is modified? Here is my use case, I have several different types of nodes. Some of these nodes are quite complex and just dropping a new node that creates a new <task> element in the source is not productive enough. I would like to be able to attached a "pre-action" for the drop of the palette item so that I could potentially show a dialog or wizard to create something as complex as a "<task>" on my diagram. -- Greg Amerson Liferay, Inc. |