admin管理员组

文章数量:1313614

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.

Share Improve this question asked Jan 30 at 16:30 Chris LewoldChris Lewold 915 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

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.

本文标签: swtNattable FilterRow visibility state not savedStack Overflow