Thanks.  Quite clear now. That sparks a random thought that perhaps for the next person "nonLayoutEdges" might be a more obvious selector name at first glance.

Tudor Girba wrote:
Take into account the following visualization:
http://www.themoosebook.org/book/internals/famix/meta-browser

The layout is only affected by the gray edges. Although the red edges
reside in the same graph, they do not affect the position of the nodes
(like this you obtain the tree as a base map and the red edges as
extra details for a selected node). This is achieved by telling the
layout to only consider the gray edges as "userDefinedEdges".

Cheers,
Doru


On Mon, Sep 10, 2012 at 4:56 PM, Ben Coman <btc@openinworld.com> wrote:
  
Can you describe how userDefineEdges fit into the system ?


moose-technology@googlecode.com wrote:
    
Status: New
Owner: ----
CC: alexandr...@gmail.com
Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7

New issue 834 by tu...@tudorgirba.com: Roassal layouts do not properly
take into account userDefinedEdges
http://code.google.com/p/moose-technology/issues/detail?id=834

To reproduce see the example below:
| edges |
view nodes: #(1 2 3).
edges := view edgesFrom: [:each  | each - 1].
view shape line color: Color red.
view edges: #(3) from: [:each | each - 2] to: #yourself.
view treeLayout userDefinedEdges: edges

If the user defined edges would be taken into account, the tree would
appear on one line (1->2->3). Instead it appears laid out as 1->2, 1->3 .

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

      
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev