[jbosstools-issues] [JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3

[Viacheslav Kabanovich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171745#comment-13171745 ] 

Viacheslav Kabanovich commented on JBIDE-21816:
-----------------------------------------------

Pull requests adds to GTK3Utils utility method refreshTableViewerI(TableViewer) that kicks table that would not refresh UI though its model is properly refreshed. The method is applied to Deploy Image to Openshift wizard where the problem is detected.

> Table is not refreshed properly in SWT_GTK3
> -------------------------------------------
>
>                 Key: JBIDE-21816
>                 URL: https://issues.jboss.org/browse/JBIDE-21816
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, upstream
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Viacheslav Kabanovich
>            Assignee: Viacheslav Kabanovich
>             Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> This issue was found while testing JBIDE-21815 and description to that issue fits to what happens in SWT_GTK3 with table. Difference is that the other issue is caused by some model failures and can be reproduced on all OS, and this case is relevant only to SWT_GTK3 when wizard model works without failures.
> Steps for some generic wizard (Deploy Image to Openshift is an example).
> 1. Create a wizard with two pages. First page has some text input, second table. Content of table is refreshed on change of text input on the first page. Input object for the table is the same, only content provider returns new values. Table has scroll, and content should be large enough to make scroll appear (without scroll, the issue is not reproduced).
> 2. Change text input on the first page, and push 'Next->' to open the second page.
> 3. At the very first navigating to the second page, the content of the table is correct, as provided by the logic binding the text input and the table.
> 4. Go back to the first page and change text input.
> 5. Again navigate to the second page.
> 6. Failure - content of the table remains as it was for the previous text input.
> 7. Recovering - just pass mouse over the table, its data in cells passed is refreshed. That means that table model is refreshed, but rendering was not completed.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)