First I thought this was connected to the calendar and calendar functionality as related functions have started to act up lately after I started using 1.9.09 and yesterday 1.9.10. However contents of the error messages might indicate the calendar stuff just triggers something else.
There have been the occasional hickup before but nothing like this. For the first time in a long Freeplane has started displaying error messages. Unfortunately they are intermittent and not exactly repeatable in predictable fashion. With one notable exeption the attached script generates errors every single time.
One example is filling an attribute from the calendar tab and clicking on "Insert Date in Selection"
Unfortunately it seems to be difficult to reproduce. Only the first usage of the day triggers the error or so it seems.
Then there's the script (attached below) that consistently generates errors every time. I have been using it since 2018 or thereabouts. Something related either to groovy or the event handling in general.
I have where the data generated content permits sent on the autogenerated "bug-reports".
Anyway, attached is the contents of one of them. Also attached is a script that has been working well for ages that has now started generating error messages related or so it seems to dates. An error message generated by the script is also attached.
Contents of the error messages seem to indicate that it is a thread Exception in thread "AWT-EventQueue-0" that a java.lang.NullPointerException occurs.
Hope this helps.
Diff:
I have tried "downgrading" the java runtime to 1.80_31 but the issue still persists.
I wonder if these 2 lines from the errormessage are significant in some way. But then again maybe not.
at org.freeplane.features.styles.ConditionalStyleModel$Item.dependsOnCondition(ConditionalStyleModel.java:85)
at org.freeplane.features.styles.ConditionalStyleModel.lambda$dependsOnCondition$1(ConditionalStyleModel.java:319)
I use conditional styles a lot to provide visual clues regarding status etc.
Created a copy of the map where all this started.
Disabled all use of conditional styles and as of now no more error messages.
So, though I am not really really sure, it looks like that the errors in one way or another are related to conditional styling.
Please attach any map containing conditional styles where you can reproduce the error using the script and explain how to use the script so that the error can be seen.
Is it possible to anonymise a map? Or at least a more convenient way than to hand edit out the "offending" parts? If not I'll try to create a new map that can replicate the error creation.
I do understand the need for a "verification map".
This question is of general interest for other cases, so I would like to know if this is enough to anonymise the contents of nodes (or, if the previous contents somehow survive in the map): make a copy map and use the search and replace to change every text for "aaa".
As per request a sort of newish map that still exhibits the same behaviour.
version 1.9.10
Very high impact, new "stable" version released mainly because of this bug
Thank you very much for this!
You have made +three years of data and rules/styles etc. viable again!
Last edit: user0123 2021-10-04