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
I made a trivial document with just a couple of headings and a couple of lines of text underneath them.
Then, with that note open & active in Obsidian (Mac, 0.15.9), I ran your Mind Map plugin version 1.1.0
As expected, the resulting mind-map display consisted of just those two headings, as nodes.
Next, I turned two of those lines of text into bullet-points
In consequence, Mind Map displayed each of those lines as a connection-line - as per attached image.
I wondered whether or not this was intentional.
Anyone who, like me, is a heavy user of bullet points for long-ish structured content, as opposed to short presentational points (say), would appreciate a setting to disable the inclusion of bullet point text in the mind map. Ideally the ability to set a default in the plugin's overall settings and also to override this in the "currently displayed map" instance.
I hope this feature request is helpful.
The text was updated successfully, but these errors were encountered:
I made a trivial document with just a couple of headings and a couple of lines of text underneath them.
Then, with that note open & active in Obsidian (Mac, 0.15.9), I ran your Mind Map plugin version 1.1.0
As expected, the resulting mind-map display consisted of just those two headings, as nodes.
Next, I turned two of those lines of text into bullet-points
In consequence, Mind Map displayed each of those lines as a connection-line - as per attached image.
I wondered whether or not this was intentional.
Anyone who, like me, is a heavy user of bullet points for long-ish structured content, as opposed to short presentational points (say), would appreciate a setting to disable the inclusion of bullet point text in the mind map. Ideally the ability to set a default in the plugin's overall settings and also to override this in the "currently displayed map" instance.
I hope this feature request is helpful.
The text was updated successfully, but these errors were encountered: