Exported HTML5 maps don't match the original files.
Discussion Open
I use the MindManager 18 and having issues in exporting the HTML5 files using the "SHARE" Icon. The exported files are messed up and don't match the original files. Items are shifted and overlap as shown in the attachment.
Attachment 1 shows the Original File in MindManager while Attachment 2 shows a messed up HTML5 file.
Can somebody help me fixing this?
Thanks
Hi Juma and Keith,
I understand it can be frustrating when the output of the HTML5 export or publish doesn't match the original. I too have spent time adjusting the location of topics, shapes, relationship lines, etc to try and get the exported output to look how I want. In many cases maps don't depend on the exact location of objects to convey their meaning, but when they do it can be a problem.
Please be aware that we are constantly fixing discrepancies and working towards more accurate rendering for our HTML5 based apps with every release.
That said, another way to tackle this if you are looking for more accurate output is to use our HTML5 editor when creating the map. Since it's the same engine used by the HTML5 export.
I reworked Juma's map using MindManager for Microsoft Teams (available since September last year) and exported the new version to HTML5 (see attached), and now all of the topics and titles are in their correct columns.
Hope that helps =)
Hi Juma and Keith,
I understand it can be frustrating when the output of the HTML5 export or publish doesn't match the original. I too have spent time adjusting the location of topics, shapes, relationship lines, etc to try and get the exported output to look how I want. In many cases maps don't depend on the exact location of objects to convey their meaning, but when they do it can be a problem.
Please be aware that we are constantly fixing discrepancies and working towards more accurate rendering for our HTML5 based apps with every release.
That said, another way to tackle this if you are looking for more accurate output is to use our HTML5 editor when creating the map. Since it's the same engine used by the HTML5 export.
I reworked Juma's map using MindManager for Microsoft Teams (available since September last year) and exported the new version to HTML5 (see attached), and now all of the topics and titles are in their correct columns.
Hope that helps =)
Hello Juma,
There have been improvements to the HTML5 Export in later versions. I suggest you try MindManager 21 and consider upgrading if you see improvements.
Best regards,
-Marian
Hello Juma,
There have been improvements to the HTML5 Export in later versions. I suggest you try MindManager 21 and consider upgrading if you see improvements.
Best regards,
-Marian
I'm using MM21 and am having the same issue. Attached files show the difference between the mind map and the HTML5 export.
I'm using MM21 and am having the same issue. Attached files show the difference between the mind map and the HTML5 export.
Hi Juma and Keith,
I understand it can be frustrating when the output of the HTML5 export or publish doesn't match the original. I too have spent time adjusting the location of topics, shapes, relationship lines, etc to try and get the exported output to look how I want. In many cases maps don't depend on the exact location of objects to convey their meaning, but when they do it can be a problem.
Please be aware that we are constantly fixing discrepancies and working towards more accurate rendering for our HTML5 based apps with every release.
That said, another way to tackle this if you are looking for more accurate output is to use our HTML5 editor when creating the map. Since it's the same engine used by the HTML5 export.
I reworked Juma's map using MindManager for Microsoft Teams (available since September last year) and exported the new version to HTML5 (see attached), and now all of the topics and titles are in their correct columns.
Hope that helps =)
Hi Juma and Keith,
I understand it can be frustrating when the output of the HTML5 export or publish doesn't match the original. I too have spent time adjusting the location of topics, shapes, relationship lines, etc to try and get the exported output to look how I want. In many cases maps don't depend on the exact location of objects to convey their meaning, but when they do it can be a problem.
Please be aware that we are constantly fixing discrepancies and working towards more accurate rendering for our HTML5 based apps with every release.
That said, another way to tackle this if you are looking for more accurate output is to use our HTML5 editor when creating the map. Since it's the same engine used by the HTML5 export.
I reworked Juma's map using MindManager for Microsoft Teams (available since September last year) and exported the new version to HTML5 (see attached), and now all of the topics and titles are in their correct columns.
Hope that helps =)
---