Looks like there is a problem when setting mappings for both node border
width (discrete) and node color (continue). For the moment, I solved the
fact that node borders are sometimes set to 2.0 (hard-coded default for
that property) when changing a node attribute (especially interesting
for us when we change the node activity) by adding a secondary thread
that waits 200 ms after the last modification to the JSlider in the
results panel and does the operations to re-apply the visual style and
update the network view. In this way we get back the correct borders
shortly after releasing the slider. The thread is kept unique to avoid
spamming them with multiple clicks/keyboard arrow presses.
Better than nothing, until a proper solution has been found.