Collapse-expand usage about org-chart HOT 10 CLOSED

Do you have any strict rule that may cause this situation? Like, the root node's expanded property must be true all the time.

This was my initial thought, but I checked that case and it was working well. Root node flag does not matter at all, it can't be collapsed, so it will be always visible

from org-chart.

Hello David, I can absolutely confirm that, it was my fault. When I was trying to rotate the tree to horizontal, I just broke the old position and enter/exit properties for nodes and paths. I have just realized and solved the problem. This is not a possible bug anymore :)

from org-chart.

That's great to hear, thank you for letting me know. I was kind of worried about it

from org-chart.

Hi @caginbektas , I tried fitting that data to the org chart, but it looks like they aren't exactly compatible and I got an error, can you reproduce the issue on sample jsfiddle and link it, so I can check what's happening?

from org-chart.

Hello,

Appreciated your jet-fast answer.

So sorry, forgot to mention that and upload the edited JS file. You can find it as attached.
(on the top, i am using the draw method to update the graph on the fly if needed.)

App1.js.zip

from org-chart.

Sorry, still can't reproduce

For me, it works as expected

You can edit this JSFiddle template, reproduce the issue, save and share a saved version with me, then I'll take a look

from org-chart.

Hello,

I have some operations using the click event of the expand circles. I might be broking it during the typescript part. I will check the code once again.

Do you have any strict rule that may cause this situation? Like, root node's expanded property must be true all the time..

Let's close this issue, i will need more investigate on that, because i disabled the typescript part, it was working without any problem.

from org-chart.

Hello,

I am still investigating, but it seems like, I am disturbing the data during my TypeScript operation. Actually, the basic requirement is, as you can see my video in the first post, I want to highlight to path which is being followed by user.

By way is every circle-button click, I am reading the current json, converting to ts object, get childs and parents of the clicked node, edit the border options in objects, convert it to json again, and call the entire js file with that new data.

Maybe you can recommend something for that? Otherwise it does not make sense to keep this issue as open because obviously error is not caused by your source code, it is in my typescript code.

from org-chart.

I am still investigating, but it seems like, I am disturbing the data during my TypeScript operation. Actually, the basic requirement is, as you can see my video in the first post, I want to highlight to path which is being followed by user.

Yes I saw that

By way is every circle-button click, I am reading the current json, converting to ts object, get childs and parents of the clicked node, edit the border options in objects, convert it to json again, and call the entire js file with that new data.
Maybe you can recommend something for that

I am not sure about the data processing step and how heavy it is, but on the org chart side, that's how it should be. Changed data redraws the graph, based on passed parameters. I could expose some function, which would take only data and would update the graph, but I chose to redraw whole chart, based on data - d3 is smart about it and only updates part, where data is changed, so no important performance hit here and it's more flexible

from org-chart.

Hello,

The reason is obviously coming from my backend customization. I am closing the issue, I will ping you back, if I will find anything related with your code (which I do not think so)

Thanks

from org-chart.