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 badges1 Answer
Reset to default 0You 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
版权声明:本文标题:swt - Nattable FilterRow visibility state not saved - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1741951046a2406707.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论