[
https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-21816:
---------------------------------------
{quote}
Do you have enough entries in tables for them to display vertical scroll? Without that
scroll, table is rendered correctly.
{quote}
I have tried to resize the wizard in order to show the vertical scroll, but it isn't
shown even though there are enough entries.
That is the same for GTK 3.10, GTK 3.14 and GTK 3.16.
{quote}
What Linux distro are you using with 3.10?
{quote}
Ubuntu 15.04 (GTK 3.14.3), compiled GTK 3.10.8, GTK 3.16.7 and GTK 3.18.7
{quote}
I have fc23/GTK 3.18 and I never experienced JBIDE-21038.
{quote}
I have tested Ubuntu 15.04, compiled GTK 3.18.7, Mars.2, JBT 4.3.1 nightly as follows:
- created Openshift 3 connection with a token on the secure storage
- restarted Eclipse
- tried to open the Openshift connection
The Secure Storage Password wizard isn't shown. It shows up when I minimize all
editors/views or exit Eclipse.
The issue is always reproducible. It doesn't happen on Neon or GTK3 <= 3.16.
The patch for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=478962 fixes the issue.
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)