| Summary: | The ability to specify a 'parent' node for generated graphs would be useful | ||
|---|---|---|---|
| Product: | [Technology] STEM | Reporter: | Stefan Edlund <sedlund> |
| Component: | Analysis | Assignee: | James Kaufman <jhkauf> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | matthias.filter |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Stefan Edlund
Discussed this with Jamie. Another solution is to create a new graph generator that tessellates the parent node. However, we might still want to create a parent node for all the graphs we generate so we can generate migration edges for a single graph only. assigned to jk (In reply to comment #2) > assigned to jk I'm not sure whether it is reasonable. but this bug sounds somehow related to the extension of the Pajek2STEM-import that Jan is currently working on, where we want to give the user the option to include a pajek graph into an existing node of a graph within the workspace. Matthias New idea... can we have an option on the graph generator to select multiple nodes and a button "create parent node" which would add a node along with the required containment edges? Let's discuss on a future call... |