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
Agreed and will be added to the 0.3 release. In the meantime, an (admittedly hacky) workaround is to use CSS to set all text elements in an alchemy instance to "display: block."
.alchemytext {
display: block !important;
}
The !important signifier is there to ensure it doesn't get overwritten by any of the many programmatic events that happen during initialization or user-interaction. Because we are moving to entirely programmatic styling in 0.3, the added configuration option will not have that problem.
If you require more control over when they show and when they don't, the javascript:
Even after adding the edgeCaptionsOnByDefault:true, I am not able to get the edges to display the text by default. Please note that the the similar option does work for nodes though by setting nodeCaptionsOnByDefault:true. I am using version 0.4.2 of alchemy.js
There should be a way to do this with a single configuration option.
The text was updated successfully, but these errors were encountered: