Topic: events fire too early (oncheck etc.)
Maybe this is not a bug, but I think it is one anyway.
onCheck (and related onUncheck, switch) events fire at the start of the method 'switch'.
If you use these events to do some JS (e.g. run getSelected and update a value somewhere) then you don't get the latest collection of checked checkboxes.
Why can't they be at the end of the method? I have done so now in my mif.tree-trunk.js for both the switch and check/uncheck events.
Any thoughts?
