Community
Participate
Working Groups
Created attachment 248437 [details] Example of rendering error Using a Sirius editor, we want to create a crosstable with ~230 columns and ~230 rows. If you scroll this table far enough towards the right, the horizontal lines disappear and no data is shown anymore. See attachment for an example. We can reproduce this both Sirius 1.0.1 and 2.0.0.
Created attachment 248634 [details] An example to reproduce
non reproductible with sirius 2.0 on windows 64bits using the attachment 248634 [details](ecore metamodeler) with more than 230 lines and columns
(In reply to Laurent Fasani from comment #2) > non reproductible with sirius 2.0 on windows 64bits using the attachment > 248634 [details](ecore metamodeler) with more than 230 lines and columns I used windows Seven 64bits
Hi, we don't reproduce, neither on Linux, neither on Windows with the attached example. Can you provide an example with steps to reproduce? Best Regards.
I can not reproduce either (tested on current master, Linux 64bits, Gtk3), closing as WORKSFORME. Don't hesistate to reopen if you can provide more information, but even Laurent who is under Windows could not reproduce, so we can not do much as it is.
We are experiencing the exact same issue on our end with Sirius 2.0.0 on Windows 8 64-bit. Any crosstable with more than ~70-80 columns exhibits serious (i.e. show-stopping) rendering issues when scrolling horizontally. Performance also degrades very severely, with any user action taken on the crosstable lagging several seconds. As far as we can tell, the root cause of the issue is that the crosstable implementation is built on top of a SWT Tree with columns which, as is the case for SWT Table, is designed to handle large numbers of rows but no more than a handful of columns, i.e. more like a database table than an Excel spreadsheet. Needless to say, this is a pretty serious issue for us as it effectively prevents crosstables from being useful for any substantial dataset.
Adding the Louis-Frederic comment, there are already well known issues with large number of columns in SWT Tree such as https://bugs.eclipse.org/bugs/show_bug.cgi?id=72293 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=302248, so reproducing it should not be an issue. Resolving it might be a different story.
