Eclipse Community Forums: NatTable » Hided dynamic column whose header is persisted leads to refresh issues

Home » Eclipse Projects » NatTable » Hided dynamic column whose header is persisted leads to refresh issues(Persisted state of header columns)

Show: Today's Messages :: Show Polls :: Message Navigator

Hided dynamic column whose header is persisted leads to refresh issues [message #1739868]

Fri, 05 August 2016 07:31

Martin Manthey

Messages: 7
Registered: March 2016

Junior Member

Hello,

we still use nattable version 1.3.0.

Our table saves the state of header columns.

In the first case the nattable shows column A and B, the user hides the column B and the nattable persists the state of header.

After that in the second case the nattable switch to another data model with column A and C, the column B does not exist in this data model.
The nattable try to show the data model and load the persisted state of the header of the first case. This leads to refreshing problems, all cells remain empty, only the grid lines are shown (see the screenshot).

This circumstances occurs only, if the a column is hided and in another case this column does not exist any more and the persisted state can not retrieved for the missing column.
And no exceptions are thrown.

best regards

Attachment: nattable_screenshot.png
(Size: 3.10KB, Downloaded 95 times)

Report message to a moderator

Re: Hided dynamic column whose header is persisted leads to refresh issues [message #1739873 is a reply to message #1739868]

Fri, 05 August 2016 08:32

Dirk Fauth

Messages: 2902
Registered: July 2012

Senior Member

This is a forum and not a bug tracker. Please file a ticket and provide a small example to reproduce the issue. I suppose an exception is thrown on loading the state.

Report message to a moderator

Re: Hided dynamic column whose header is persisted leads to refresh issues [message #1739874 is a reply to message #1739873]

Fri, 05 August 2016 08:41

Dirk Fauth

Messages: 2902
Registered: July 2012

Senior Member

After thinking more about that issue, why do you expect that the table should automatically deal with states for different table models? IIRC you are storing the table state for data model A, then you change the data model to B and try to load the state for A. I assume the exception that is raised tells that the data model and the table state doesn't match.

The more I think about that, the more I think the issue is a user issue, not a NatTable one.

Report message to a moderator

Previous Topic:	ZoomLayer
Next Topic:	Remove selection anchor

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 03:20:40 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter