You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear coders,
I am not entirely sure if this is place to post a question/petition.
When given the name to the nodes all works nicely according to the examples given.
The names "node1", "node2" are very short.
If the names are given a very long name (a paragraph of a text) the line will get out of the screen and it will not be possible to see it completely.
Is there any plan to include a parameter for displaying width=X where x is a number of characteres and hence the display with node names with more than X characters will be displayed in multiline (wrap text modus).
The text was updated successfully, but these errors were encountered:
joseberlines
changed the title
Is there any plan for allowing multiline names per node?
Is there any plan for allowing multiline lines per node name?
Jan 26, 2020
Hi, so cool to make this an enhancement.
I guess we are all use to see this tree structures as folders (i.e. short names).
Reality is that this tree structure is also applicable in law texts, where there is a dependency of paragraphs along a text document.
Dear coders,
I am not entirely sure if this is place to post a question/petition.
When given the name to the nodes all works nicely according to the examples given.
The names "node1", "node2" are very short.
If the names are given a very long name (a paragraph of a text) the line will get out of the screen and it will not be possible to see it completely.
Is there any plan to include a parameter for displaying width=X where x is a number of characteres and hence the display with node names with more than X characters will be displayed in multiline (wrap text modus).
Thanks.
I already publish a Q in StackOverflow:
https://stackoverflow.com/questions/59900288/jupyter-notebook-ipytree-multiline-node
The text was updated successfully, but these errors were encountered: