Bug #430

RCP: x.x, Windows : Table sorting is too slow on some tables

Ajouté par Sebastien Jacquot il y a presque 4 ans. Mis à jour il y a plus de 3 ans.

Statut:Feedback Début:25/10/2013
Priorité:Normal Echéance:
Assigné à:- % réalisé:

0%

Catégorie:UI / Interaction Temps passé: -
Version cible:TXM 0.8

Description

Table sorting is too slow on some tables on Windows, eg on a lexical table with 64 parts, it can sometimes take about 50 secs.
Bug linked with the columns auto-size calculation ?

Historique

#1 Mis à jour par Sebastien Jacquot il y a plus de 3 ans

  • Statut changé de New à Feedback

Could someone confirm this bug on Linux or Mac ? (So we could exclude that's a native bug)

Steps to reproduce :
- create a partition text.annee on VOEUX corpus
- compute specificities on this partition (54 parts)
- click on "Units" to sort rows in reverse order

- it takes almost 50 seconds on my Win 7 64 bits before the UI stops refresh
- the refresh seems to be done more than one time, during first refresh the UI is locked but during the next refresh it seems we can change active tab (it stops the refresh ?)

#2 Mis à jour par Sebastien Jacquot il y a plus de 3 ans

The problem appears to be related to the columns packing. Removing it removes the bug (SpecificitiesTableEditor.class).

    /**
     * Fill display.
     */
    private void fillDisplay() {
        viewer.setInput(tableLines);
//        for (int i = 0; i < specificitesTableColumn.size(); i++) {
//            specificitesTableColumn.get(i).pack();
//        }
        //specificitesTable.getParent().layout();
        //viewer.refresh();
    //        for (TableColumn col : specificitesTable.getColumns())
    //            col.pack();
    }

Packing the columns can do the label of the sort column is not truncated (due off the sort order arrow display).

The problems are :

1) if we don't pack :
- the label of the sort column is truncated because of the sorting order arrow display

2) if we pack only the sort column
- the old sorted columns are not repacked therefore their width stays the same as if the label contains a sort order arrow

The solution 2 seems to be the best at the moment.

#3 Mis à jour par Sebastien Jacquot il y a plus de 3 ans

Finally don't we need to keep the user defined column widths et do not pack at all ?
Truncation of labels is perhaps not important compared to keep what the user did?

This bug has been noticed in the specificities, the index and the lexical table.

Formats disponibles : Atom PDF