[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21816 at 3/3/16 8:56 PM:
-----------------------------------------------------------------------
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.
The separate pull request for branch 4.3.x: https://github.com/jbosstools/jbosstools-openshift/pull/1006
was (Author: scabanovich):
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)
10 years, 1 month
[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ]
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)
10 years, 1 month
[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3662:
-------------------------------------
What does it mean "full and perfect"? Could you post what you have in this dialog?
> CDK Launch config has broken PATH env variable value set
> --------------------------------------------------------
>
> Key: JBDS-3662
> URL: https://issues.jboss.org/browse/JBDS-3662
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: path.png
>
>
> Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21797:
-------------------------------------
The issue seems to be caused by an update to teh response to vagrant status --machine-readable.
{code}
1457045944,cdk,state,running
1457045944,cdk,state-human-short,running
1457045944,cdk,state-human-long,The blahblahtruncated
1457045944,,ui,info,Current machine states:\n\ncdk blahblah truncated
{code}
The last line is only in vagrant 1.8.x, and you can notice the second field is empty. This breaks our expectations as they were coded for vagrant 1.7.x.
PR is available https://github.com/jbosstools/jbosstools-openshift/pull/1004
> Fails to start the CDK server when it's was already started from CLI
> --------------------------------------------------------------------
>
> Key: JBIDE-21797
> URL: https://issues.jboss.org/browse/JBIDE-21797
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI
> - once it's started, start the same CDK from the CDK server adapter
> => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with
> !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3662) CDK Launch config has broken PATH env variable value set
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3662?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3662:
-------------------------------------
Nothing, just started JBDS after installation.
> CDK Launch config has broken PATH env variable value set
> --------------------------------------------------------
>
> Key: JBDS-3662
> URL: https://issues.jboss.org/browse/JBDS-3662
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: path.png
>
>
> Why it duplicates what is already set on installer side? Installer configures everything that is required for vagrant .up to work except SUB_USERNAME and SUB_PASSWORD.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21815 at 3/3/16 5:16 PM:
-----------------------------------------------------------------------
Well, after trying all kinds of refreshes that were of no use at all, I found one strong remedy, and I know that everyone will be disgusted with it, but it is the only one that works:
{code}
@Override
protected void onPageActivated(DataBindingContext dbc) {
if(envViewer != null && envViewer.getControl() != null && !envViewer.getControl().isDisposed()) {
Object input = envViewer.getInput();
envViewer.setInput(null);
envViewer.setInput(input);
}
if(dataViewer != null && dataViewer.getControl() != null && !dataViewer.getControl().isDisposed()) {
Object input = dataViewer.getInput();
dataViewer.setInput(null);
dataViewer.setInput(input);
}
}
{code}
I remind that table fails update on its own only when it needs vertical scroll, so it is entirely an UI problem, not model updating and not databinding.
As what I found turns out to be a GTK3 problem, I have created issue JBIDE-21816 because it does not cover what caused this issue on Mac OS.
was (Author: scabanovich):
Well, after trying all kinds of refreshes that were of no use at all, I found one strong remedy, and I know that everyone will be disgusted with it, but it is the only one that works:
{code}
@Override
protected void onPageActivated(DataBindingContext dbc) {
if(envViewer != null && envViewer.getControl() != null && !envViewer.getControl().isDisposed()) {
Object input = envViewer.getInput();
envViewer.setInput(null);
envViewer.setInput(input);
}
if(dataViewer != null && dataViewer.getControl() != null && !dataViewer.getControl().isDisposed()) {
Object input = dataViewer.getInput();
dataViewer.setInput(null);
dataViewer.setInput(input);
}
}
{code}
I remind that table fails update on its own only when it needs vertical scroll, so it is entirely an UI problem, not model updating and not databinding.
> Image metadata not refreshed after name change
> ----------------------------------------------
>
> Key: JBIDE-21815
> URL: https://issues.jboss.org/browse/JBIDE-21815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
>
> Steps to reproduce:
> - open the *Deploy Docker Image* wizard
> - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}}
> - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again.
> - ASSERT: the metadata should have been updated
> - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21816:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> 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)
10 years, 1 month
[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-21816:
------------------------------------------
Workaround Description:
Workaround is kicking table at page activation with the following code:
{code}
if(viewer != null && viewer.getControl() != null && !viewer.getControl().isDisposed()) {
Object input = viewer.getInput();
viewer.setInput(null);
viewer.setInput(input);
}
{code}
It may seem too strong, but all other attempts to use update() layout() refresh() have not succeeded yet.
was:
Workaround is kicking table at page activation with the following code:
{code}
if(viewer != null && viewer.getControl() != null && !viewer.getControl().isDisposed()) {
Object input = viewer.getInput();
viewer.setInput(null);
viewer.setInput(input);
}
{code}
It may seem too strong, but all other attempts to use update() layout() refresh() have not succeeded yet.
> 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.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)
10 years, 1 month
[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-21816:
---------------------------------------------
Summary: 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.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)
10 years, 1 month