Posted on the forum yesterday (https://sourceforge.net/projects/freemind/forums/forum/320014/topic/4737280) and submitted here as requested, but with changes following a re-run today to confirm functionality:
I've had Freemind for a little while but am starting to try more of the functions. Currently, I have a problem with the 'Show Revisions in Yellow' function, which seems to behave in ways which make it unusable. I see that someone asked a question on this feature back in version 0.8 (https://sourceforge.net/projects/freemind/forums/forum/22102/topic/3484946) but unfortunately the post is unanswered and as far as I can see this is a problem which remains in version 0.9.0 (unless I have missed something).
After selecting the 'Show Revisions in Yellow' option either the first time on opening the application or when the option is already set on opening, the new nodes and edited nodes turn yellow as expected; however, behaviour is otherwise unexpected as follows:
1) Once highlighted as changed, there is no complementary function which appears to operate to clear the highlighting when appropriate, and re-starting the application does not force a reset either. This causes two cases in point:
i) After editing a node - which correctly becomes set to yellow as a result of being edited - if the edit is 'undone' the colour does not revert to it's normal colour (i.e. the node remains incorrectly highlighted as changed); NB I can confirm that any such errors are not corrected by a re-start.
ii) After saving a file, changes made prior to the save remain highlighted as changed.This is unexpected functionality, as all highlights would be expected to clear (since by virtue of a save, the changes have been accepted as firm by the user).
3) After the option is cleared, although the menu indicates that it can be set again, in reality the function will not operate again until the application is re-started. NB This seems to be the case regardless of whether the function is first activated in a session by (i) the option being set manually within a session, or (ii) being pre-set on application start (by virtue of being previously set).
Otherwise I'm very optimistic of finding the program more and more useful as I discover more functionality!
I would be very grateful to developers if these problems could be confirmed and if some indication of when a version with this function fixed may become available. Thanks very much! Garrog.