| SizeConfig doesd not invalidate cache when DPI converter is set [message #1773754] |
Wed, 04 October 2017 03:37  |
Eclipse User |
|
|
|
Hi,
I think that a call to org.eclipse.nebula.widgets.nattable.layer.SizeConfig.setDpiConverter(IDpiConverter) should invalidate the internal aggregate size cache by setting:
isAggregatedSizeCacheValid = false;
We experience layout problems in displays with high resolution. We found out that the reason is that some aggregated sizes are already calculated during initialization of the DataLayer (namely the secondlast column and the last column).
Then upon initialization of the NatTable in internal setLayer the ConfigureScalingCommand is performed which sets a DPI converter in the SizeConfig of the DataLayer. The cached data of SizeConfig is now invalid because it was calculated without the dpi converter whereas all further calls to getAggregateSize will respect the upscaling due to the dpi converter.
Layoutproblems occur if due to this upscaling the positions of other columns extend the cached position of the secondLast column.
Should I raise a ticket on this?
Regards,
Thorsten
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03226 seconds
Home