That's interesting, thanks Stoyan.
Do the nodes have to be locked for this to work? The reason I ask is that I shortly need to add code to 'roll up' some of the lanes.
What I have to achieve is to effectively make the lanes work like containers. The lanes in our system represent hierarchical data, e.g.
Lane 1
-Lane 1.1
--Lane 1.1.1
-Lane 1.2
Lane 2
The client wants to represent the data as lanes, but wants to be able to minimise the data below a certain point in the hierarchy, e.g. to rollup all lanes below Lane 1 (1.1 and 1.1.1 in the example above). There is a fairly reasonable aim for this, which is to allow 'summary' views of the data to be printed with only the top-level processes (which are represented by the lanes) to be displayed.
However, they still want to see the links that are connected to nodes in Lane 1 that join with nodes in the (now rolled up) lanes 1.1. and 1.1.1.
My plan for this was to replace lanes 1.1 and 1.1.1 with a single lane that contains all of the nodes that were in 1.1. and 1.1.1 and retains their horizontal positions, and then to draw one (probably very wide) node across the whole new lane on top of the 'real' nodes. The hope is that all the links will therefore keep working.
How this relates to the nodes as lanes question is that I was considering using nodes for lanes so that I could create a custom lane node that had a minimize/maximise button, but if this node has to be locked then I may be better just placing a node on top of the grid's row headers.
Any general thoughts you or your team have about the above (i.e. is it a really stupid idea) would be very gratefully received!!
![Smiley Smiley](https://mindfusion.eu/yabbfiles/Templates/Forum/default/smiley.gif)
Thanks
Tom