Fix settings propagation in tree

[kloggy]

I see that there was an issue that appeared to address (490678d, closed on 13 Jan) but I still see topics in a 'random' ordered list.

Thanks.

[thomasnordquist]

Thanks for reporting 👍.
The problem here is that the new "topic order" is not immediately propagated to nested topics, only when a child topic receives an update.

Quick Fix:
Collapsing and expanding the "root" node (or simply reconnecting) will resolve this issue.

I'll keep you posted when it is fixed and when the fix has been released, there are also a few other things I'd like to put in the next release.

[kloggy]

That's great thanks. I was using MQTT.fx until I found this and I far prefer this!

[thomasnordquist]

Glad to hear it =)

[kloggy]

Although....
From this to this:

To this:

doesn't seem to re-sort. (Just so you know)

[thomasnordquist]

Note to myself: I also noticed this behavior for the "Quick Preview" option.
I should probably start using immutables (immutablejs) to guarantee the propagation of settings/values in the tree.

Directly connecting the nodes to the store is not possible since it would have a huge performance impact on every store update, even if store changes are unrelated to the topic. (10k nodes ~150ms, just propagating store updates)

[thomasnordquist]

Fixed with 436b569.