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.
1 Answer 1
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.
answered Jan 30, 2025 at 19:35
Dirk Fauth
4,2412 gold badges16 silver badges25 bronze badges
Sign up to request clarification or add additional context in comments.
1 Comment
Chris Lewold
That's a good hint for the future, when I want to persist own attributes related to NatTable - thanks Dirk. I mainly had the idea to implement it as a Subclass, as I thought it actually should belong into FilterRowHeaderComposite anyways (actually it's a NatTable state attribute, that currently doesn't get persisted, in contrast to e.g. column positions).