Actions might resolve each other (e.g., open/close, select/deselect) or could be combined (e.g., multiple subsequent single selections could be combined to one multi-selection).
I assume that the compressor is application specific, since it depends on the registered actions. However, we should provide a basic implementation and test cases in the core, since it influences the tree traversal.
Actions might resolve each other (e.g., open/close, select/deselect) or could be combined (e.g., multiple subsequent single selections could be combined to one multi-selection).
I assume that the compressor is application specific, since it depends on the registered actions. However, we should provide a basic implementation and test cases in the core, since it influences the tree traversal.