elk icon indicating copy to clipboard operation
elk copied to clipboard

Eclipse Layout Kernel - Automatic layout for Java applications.

Results 214 elk issues
Sort by recently updated
recently updated
newest added

**Describe the bug** See https://github.com/eclipse-elk/elk/issues/1178#issuecomment-3612878286 **Screenshots** **ELK Version** 0.11.0 **Additional context** I tink the description of some group model order options should be more complex.

bug
chore

**Describe the bug** I've come across an issue where using the `layered.considerModelOrder.strategy` option set to `PREFER_NODES` can lead to a different layout as soon as you use it in conjunction...

bug
alg-layered

Using Port side constraints with certain layout directions causes bad layouts in unpredictable situations. In the following graph the edge labeled "t" should connect to a port on the WEST...

bug

I'm using org.eclipse.elk.core and org.eclipse.elk.alg.layered as maven dependencies. After upgrading to 0.11, I'm getting java.lang.NoClassDefFoundError: org/eclipse/xtext/xbase/lib/CollectionLiterals Which is caused by an import org.eclipse.elk.alg.layered.options.LayeredMetaDataProvider Is this a bug (wrongly added import)...

bug

**Describe the bug** `crossingMinimization.forceNodeModelOrder` causes a NullPointerException when `INCLUDE_CHILDREN` is set. Minimal graph: ``` graph root algorithm: layered hierarchyHandling: INCLUDE_CHILDREN node container { crossingMinimization.forceNodeModelOrder: true node childOne { layout [...

bug

allow putting each node in a split layer alone in a sublayer removes an unnecessary restriction in the layer splitting option

alg-layered

This should fix all the problem I have with people sending me json graphs that need to be converted to elkt. Often these graphs have ids that begin with letters,...

Unfortunately, I can't share any reproducible example. I use ELK Layered, the offending option is hierarchy handling which is set to INCLUDE_CHILDREN. With SEPARATE_CHILDREN everything works. I think the diagram...

bug

I was looking through the `bk` node placer implementation, and saw some comments about overlapping nodes and layer-ordering violations. In case you haven’t seen it, there’s an [erratum published in...