Eclipse Community Forums: NatTable » SpanningDataLayer paint problems when scrolling fast

Home » Eclipse Projects » NatTable » SpanningDataLayer paint problems when scrolling fast

SpanningDataLayer paint problems when scrolling fast [message #1697692]

Sat, 06 June 2015 03:59

Eclipse User

Hi,
when using the SpanningDataLayer in a large table, paint artifacts occur when initially scrolling down the table (fast). It looks like the lines which should be invisible (because of spanning) are painted. Of course if scrolling stops everything is rendered correctly. Once the table has been scrolled down completely and every part was rendered once, everything is fine and fast scrolling works without those ghostlines. Is there some command that I could use in order to precalculate the necessary information to do a proper rendering from the very beginning?

Thanks in advance
Thorsten

Re: SpanningDataLayer paint problems when scrolling fast [message #1697693 is a reply to message #1697692]

Sat, 06 June 2015 05:56

Eclipse User

Is this because of spanning or are you using a TextPainter with dynamic size calculation? Sounds more like the later.

Re: SpanningDataLayer paint problems when scrolling fast [message #1697751 is a reply to message #1697693]

Mon, 08 June 2015 03:40

Eclipse User

Yes that is true. I am using a TextPainter with dynamic size calculation. Is there a command that pre-calculates the correct row heights to overcome this problem. I am using the InitializeAutoResizeRowsCommand and thought that this would do the trick. Therefore I thought it was in issue with the spanning.

Re: SpanningDataLayer paint problems when scrolling fast [message #1697752 is a reply to message #1697693]

Mon, 08 June 2015 03:41

Eclipse User

If it is related to dynamic row height calculation using the TextPainter, the workaround is to perform autoresizing when loading is finished. A possible solution is described here: https://www.eclipse.org/nattable/documentation.php?page=faq

Note that this shouldn't be used with large tables, since it violates the virtual nature of NatTable and can cause serious delay in rendering at the beginning. For smaller tables this might be a suitable workaround.

Previous Topic:	Nattable menu invocation when table is empty
Next Topic:	Alternating Row Configuration

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 08 11:27:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter