The example shows how to implement a custom port to provide a fast configuration option. It is not always necessary to implement full blown dialogs or property panes. Sometimes the tiny smartway ist the best way. Just a mouse click away.

+attributes not applied/set to a label figure if it has been removed and added again to the canvas - fixed.+new events fired for "dragstart", "dragend", "mouseenter" and "mouseleave" for figures, resize handles and ports+"growing" ports during connecting two ports is solved.+fire events "connect" and "disconnect" on ports if a connection is deleted+add "padding" to the horizontal and vertical layout shape+fixing "gap" calculation in horizontal layout+invoke missing layout recalculation if a child->child element has changed the dimension.+add "margin" as attr property to the LeftLocator/RightLocator constructor to drive the distance between child and parent.+move Connection.insetPoint method to new draw2d.geo.Util scope+fixing rendering problem in the "Polygon" element. The rendering is always "one behind" the mouse movement.+new example. Show how to implement a port decoration which can be toggled off/on by the user.

+ fixing major bug in getter/setter handling for attr-calls.+ add missing function Label.getFontFamily+ check recursive for click event on children of line+ change order of click event check. lines now the last candidate for a click event

The idea behind 2-way databinding is managing model-view updates in two directions. First, views are updated when a model changes, which is the default case for 1-way databinding. Additionally, views can directly update models, which is a second update “direction”, hence the name “2-way databinding”.

+bugfixes for IE8+ new event "routed" is fired when connection is recalculated.+ adding polyfill method for Array.reduce to support IE8.+ new method Figure.getRoot to get the top most parent of a figure