yFiles FLEX 1.4.0.2 Release Notes

The newest available bugfix and maintenance release of yFiles FLEX is version 1.4.0.2.

Technical Requirements

Flex 3 SDK for software development of yFiles FLEX-powered web applications for Adobe Flash Player 9 (or higher).
Adobe Flash Player 9 (or higher) on the client to execute yFiles FLEX-powered web applications.
For automatic graph layout on the server, either yFiles for Java Complete (2.6 series, at least 2.6.1) or yFiles.NET Complete (3.2 series, at least 3.2.1.2).
A servlet container (for example, Apache Tomcat) is required, if yFiles FLEX is combined with yFiles for Java.
Sun Microsystems J2RE 1.4 (or higher) on the server, if the yFiles for Java library is used.
Visual Studio is recommended as IDE, if yFiles FLEX is combined with yFiles.NET.

Fixed a bug in the FoldingLayoutStage that caused an Exception when handling selfloop edges at children of collapsed nodes.
Fixed a bug in GraphCanvasComponent#morphGraph that prevented correct disabling of auto adjusting group node bounds during graph layout animations of folded graphs. This sometimes resulted in incorrect group node bounds after layout animations of folded graphs.
Fixed a bug in FoldedGraphWrapper which caused an Error when the wrapper was initialized with a non-empty graph.
GraphMLIOHandler: The GraphEvent which is dispatched after reading a graph now contains the parsed graph instead of the master graph if the graph is a folded graph.
GraphCanvasComponent: loadGraphFromURL() doesn't replace a folded graph with its master graph anymore.
MagnifierInputMode: an IDisplayObjectContext is now used for rendering inside the magnifier "Lens". Items using TemplateStyle are now correctly enlarged with the magnifier.

yFiles FLEX (Java Server Bundle): upgraded to yFiles for Java 2.7
yFiles FLEX Client: added server side libraries for compatibility with yFiles for Java 2.6 and 2.7

Changing the port location programmatically now forces a repaint of edges which start/end at that port
Fixed an Error in the context of IFoldedGraph that could happen in multi-level node collapse operations as a result to calls to collapse