Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KChildArea within other container rendering causes misplaced nodes #25

Closed
NiklasRentzCAU opened this issue Apr 9, 2020 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@NiklasRentzCAU
Copy link
Member

In the current master, the following .kgt file causes a weird Layout:

kgraph hierarchicEdge
properties:
de.cau.cs.kieler.kgraphsynthesis.defaults = true
org.eclipse.elk.hierarchyHandling = INCLUDE_CHILDREN
org.eclipse.elk.direction = RIGHT
knode {
	krectangle {
		grid: columns = 1
		ktext("foo")
		krectangle {
			kchildArea
		}
	}
	knode src {
		kedge (-> dest:p_dest)
	}
	kport
}
knode dest {
	kport p_dest
}

 KLighD will show the graph like this in a diagram:
childInContainer.png

The edge should be a straight line leading into the destination port, not somewhere way above that. Also, the additional single port added to the left of the hierarchic node should be centered and not somewhere above the center.
Both these effects are affected by the offset of the child rendering within its node. Adding some linebreaks "\n" to the text above the renderings makes both these issues even worse.

@NiklasRentzCAU
Copy link
Member Author

This issue is migrated from the old KIELER Pragmatics JIRA issue tracker. See the old discussion on this ticket in KIPRA-1980.

@NiklasRentzCAU NiklasRentzCAU added the bug Something isn't working label Apr 9, 2020
@NiklasRentzCAU
Copy link
Member Author

Fixed with #154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant