-
Notifications
You must be signed in to change notification settings - Fork 119
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
Manually control horizontal position of nodes? #227
Comments
+1 This would be super useful feature for displaying datasets that have explicit start and end times for frames. Currently it ends up displaying a left skewed flamegraph by displaying child start == parent start @LinqLover I ended up implementing something similar to add dummy spacer nodes, but unable to figure out how to style them (to make them transparent). Mind sharing how you made them hidden? Update:
|
@hrishikeshdok Yes, pretty much this was also my approach. If you still need it, you can find my full code here: Interestingly, CSS overrides were not required for me ... |
Is your feature request related to a problem? Please describe.
I am visualizing a program trace using this nice package and want to display the exact progress over time. So, every node has a time interval. However, this package has no support for this, I can only provide a duration (endTime - startTime) for each node, and somehow the nodes are then layouted using d3-hierarchy's partition mechanism.
Describe the solution you'd like
Ideally, the possible input format would be extended like this:
If not both values are specified, the layout would still work as before. Some kind of error checking for out-of-parent times etc. might be appropriate.
However, I'm not sure whether this is in the scope of this project. But it would be great!
Describe alternatives you've considered
My current workaround is to transform my program trace into a hierarchy for d3-flame-graph where all "gaps" between nodes are filled up with transparent spacer nodes:
And then I wrap all other functions (label, color, etc.) to answer null/transparent for the dummy nodes. But you can imagine the overhead in terms of inner complexity and performance.
The text was updated successfully, but these errors were encountered: