Shintaro Kojima

Still working on this issue. After my investigation, it's unfortunately difficult to cover all topologies with a fixed custom parameter like `initialTicks: 10`. The best value depends on the outline...

Thanks for the steps explained. Let me try to reproduce in my environment and investigate why inet-henge ignores levels defined in json.

I got the topology you mentioned finally.  source code: 598ba2f...4850f7f A problem I found is that some of the constraints don't work, even they look valid to me. I'm...

So do you mean SetCola ( without inet-henge ) works for you? Or inet-henge can work along with SetCola? I'm just curious.

Sounds great :tada: But yes, setPosition, translate or something like auto-layout stuff may conflict with SetCola. I'll read your codepen anyways. Thanks!

Thanks! This is awesome :tada: > So I think you can include option into Diagram class Yes, that's the last thing we have to do. I'd like to introduce a...

By the way, in your diagram mentioned [here](https://github.com/codeout/inet-henge/issues/27#issuecomment-791011190), do three groups overlap each other at the bottom, don't they?

Hi, it could be done but not supported for now. Let me try. (or your PR would be greatly appreciated)

Just pushed a newer version. Cloud you try it with the data below? ```json { "name": "192.168.3.63", "icon": "./images/server.png", "group": "GRP1" }, { "name": "192.168.35.72", "icon": "./images/server.png", "group": "GRP1" },...

Scattered manually. That inline layout is the initial state before calculation. If you add some links, inet-henge calculates them before rendering and diagram should be different.