search

TthinkModell / dynnetwork

Automatically exported from code.google.com/p/dynnetwork
0 stars 0 forks source link

A custom attribute in an <edge/> is not recognised #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Generate an xgmml containing <edge source="A" target="B" label="C" key="1">
2. Use Dynamic XGMML loader to load the xgmml
3. The key attribute is not available in the Table Panel or the vismapper

What is the expected output? What do you see instead?
the Key attribute should be shown in the Table Panel

Please use labels and text to provide additional information.

Original issue reported on code.google.com by nworbn...@gmail.com on 1 Aug 2012 at 9:09

GoogleCodeExporter commented 8 years ago 
Definition of attributes directly inside the definition of edges is not 
supported.
use instead:

<att name="key" type="integer" value="1"/>

or is it a problem?

Original comment by xani...@gmail.com on 6 Aug 2012 at 10:14

GoogleCodeExporter commented 8 years ago 
Yes, using an <att ... > is fine.

Just seems more natural for an attribute that is constant for the life of the 
<node> or <edge> to be placed as an attribute.

not important.

Original comment by nworbn...@gmail.com on 8 Aug 2012 at 1:24

GoogleCodeExporter commented 8 years ago 
I close the bug since that type of encoding will not be very compatible of how 
the XGMML parser is implemented (the finite state machine requieres a single 
attribute in each line)

Original comment by xani...@gmail.com on 21 Aug 2012 at 3:03