I use NatTable saveState/loadState logic in order to persist the current layout. This works nice, beside the visibility state of the filter row.
Is it correct, that FilterRowHeaderComposite should override saveState and loadState in order to persist filterRowVisible?
As a temp solution I implemented a subclass of FilterRowHeaderComposite, and implementing the load/save methods seems to work. I just want to know if I am on the correct path.
I use NatTable saveState/loadState logic in order to persist the current layout. This works nice, beside the visibility state of the filter row.
Is it correct, that FilterRowHeaderComposite should override saveState and loadState in order to persist filterRowVisible?
As a temp solution I implemented a subclass of FilterRowHeaderComposite, and implementing the load/save methods seems to work. I just want to know if I am on the correct path.
You could also implement an IPersistable and register it on the FilterRowHeaderComposite. This basically gives you the option to save any additional state. And you don't need to create a subclass.

