#1235 Last node usually not updated or processed

[Ali Akcaagac]

I would like to address following issue with Freemind 1.1.0 (Beta)

https://sourceforge.net/p/freemind/bugs/1234/

The following issue (which I detected out of causal ivestigation). The last element of a node is most of the time not being updated!.

How to figure this out ?

xmllint --format --nsclean "mindmap.mm" | tail -n +2 > "mindmap-new.mm"

Say again you have the 50 nodes MindMap. Now use xmllint to "format" the MindMap. This usually adjusts plenty of the embedded html tags of the richelement to the left. Nothing to worry here.

Now load the MindMap up again and repeat the processes as show in bug #1233 (bug #1234). There is no need to change anything inside the MindMap. Only select all, unfold all, free position, select bubbles, sort, fold all, save.

Loading the MindMap within an editor. The editor show that (on most of the cases: but not always) all node elements (except the last one) got re-formated (which is the expected behaviour). The only exception is the last node, which is left untouched.

I had it one time, that I edited the last node (of a MindMap consiting of two nodes) that the changes within that node is not being saved (even if the * at the top left (showing the changes) is shown).

[Ali Akcaagac]

Please find attached an example of what I mean. Note that this is straight cut out of an working mindmap. The last and second last element in the file. As you can see the second last element got it's html attributes (indented) or (formated) correctly, while the last element (and it's always the last element that contains html stuff) is not. I would really like to see it indented or formated as the previous one. Probably a n-1 issue in a for-loop.

You also see that the second last node has it's unicode (or non displayable9 values converted to decimal and the last node still has it in hex-decimal. So it's a clear sign that the last node is not being processed (for indenting, formatting and converting values from hex to dec).