Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Style inheritance

Kat Sep 18, 2017 06:40PM HKT


Honestly speaking: I bought the pro version because of the themes and style difinitions. And now I'm dissapointed beyond words. Instead of working on my mindmap and the thoughts roaming my head, I spent half of the night trying to find what's the problem to then figure out that the program's "themes" and "styles" are empty promises.

Why do I say this? Because I bought pro-version for easier mind-map creation! And what I find is, that neither do the "styles" mean, that the nodes of the same style auto-update upon changing the styley nor are the so called "themes" capable of pre-defining more than 3 layers! 3!! 3 sans the fidst main node that's 2!!! I write the header, I write nodes with years, I write nodes with months and when I get down to starting to write the actual content, the "theme" already stops applying. Which means, that from this step onwards, every new node and sub-node that I create, looks exactly the same. Even if I change their style, the new nodes will not inherit it, I constantly need to change things manually.

The only way to get new nodes with the style I need, is to copy on old node. However, this function is already available in the free version. So I'm even better off creating a 10 layerd template map than using theme-definitions.

This is something that you really can improve in future. The themes don't make things easier when they're limited to just 3 layers. What you truly need are auto-updateable style definition and style inheritance, that can choose from "inherit from parent" and "inherit from brother". As e.g. two checkboxes at the side that I can tick on and off during creation process like I can pick the colors and forms for each node.

I'll be testing this a bit further and will then remove my license key to work on and see if at this rate there are any PRO options that I'm missing at all. And if not, I'll have to make use of the guarantee. In such case I'll honestly be glad to come back and pay for an updated XMind version that can do the things above and save me a lot of time! I do not mind paying. But I don't have enough money on my hands to use it for things that don't work for me/improve my user experience at all.

If you are a user and face this problem, please comment and please upvote the comments of other users to show the developers that we're interested in solutions! I would rather have this fixed than getting back my money! :'3

Up 1 rated Down
Michael McDonald Nov 01, 2017 08:52PM HKT
I'm currently utilizing the free version; however I discovered quickly that the themes / styling are extremely limited so I started researching to see if the PRO version would offer better functionality for what I want (styling on additional layers / children / sub-topics. It appears that this is not something that is present and as such I'm glad I haven't spent my money yet. I will continue to watch Xmind to see how they develop, but at this point I'll have to hold-off.
Up 1 rated Down
ash Nov 17, 2017 02:31AM HKT
Yep the "support" for styles is very disappointing. They don't work like they should. You should be able to define infinite levels of styles, the same way you can with CSS.

Would be nice if the developers would address this. This has been a complaint of mine since i started using XMIND a few years ago. I brought it up then, and it still hasn't been addressed. It's not worth buying PRO until this is a working feature.

Not sure if many people are aware of this, but Xmind PRO is available through SetApp. SetApp gives you access to a bunch of paid apps. I think the subscription is $10/mo? It might be worth it to some if you have use for the apps they offer. I tried it for XMIND Pro, but since i'm not getting any use out of the Pro features, i'm no longer using it.

Post Your Public Answer

Your name (required)
Your email address (required)
Answer (required)
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found