[JBoss JIRA] (ERT-693) [GTK3] Combo pulldown text cutoff on Linux [EBZ#542867]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-693?page=com.atlassian.jira.plugin.sy... ]
Eric Williams resolved ERT-693.
-------------------------------
Resolution: Done
> [GTK3] Combo pulldown text cutoff on Linux [EBZ#542867]
> -------------------------------------------------------
>
> Key: ERT-693
> URL: https://issues.jboss.org/browse/ERT-693
> Project: Eclipse Release Train
> Issue Type: Task
> …
[View More]Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Created attachment 276946
> Wizard screenshot on Eclipse 4.10
> Swithcing from Eclipse 4.9 platform to Eclipse 4.10. The size computations for various of our 'pull down' style text combo widgets are now wrong. They result in text being cut-off and in some cases totally unreadable (if the text is just one character, cutting of any part of the text will do that).
> One of my coleagues tried the wizard on Mac and it looks fine there. So this looks to be a regression in Linux SWT only.
> I'm attaching two screenshots, one from before Eclipse 4.9 and one from Eclipse 4.10.
> This doesn't appear to affect all combo boxes. Some boxes are drawn correctly. I think it has something to do with the fact that the affected boxes are not on screen when the wizard is initially shown. These widgets are added later on (dynamically populated from data read from a web service) and so there are some calls being made to 'reflow/relayout' the page after the widgets have been added or their contents changed somehow.
> In fact with the wizard from which these screenshots here are taken, the widgets briefly appear on screen 'correctly' (a bit hard to be sure, as they only appear very briefly) and then they get resized to a smaller size cutting of the contents.
> When sized correctly (E 4.9) the widget's width takes into account all of these:
> 1) text in the widget currently visible on screen
> 2) the width of the little pull-down arrow.
> 3) text in the pull-down menu (i.e. the other items that can be chosen by the user could be wider, and the widget acomodates enough space to show the largest of them).
> When sized 'incorrectly' (E 4.10) what it looks like to me is that instead only the currently visible text is taken into account. It does not account for the other items in the list, nor the width of the pull-down icon.
> I'll see if I can come up with some code snippet to reproduce this problem, and, if able to, will attach it later.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months
[JBoss JIRA] (ERT-693) [GTK3] Combo pulldown text cutoff on Linux [EBZ#542867]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-693?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-693:
---------------------------------
Sprint: devex #159 December 2018
Assignee: Eric Williams
> [GTK3] Combo pulldown text cutoff on Linux [EBZ#542867]
> -------------------------------------------------------
>
> Key: ERT-693
> URL: https://issues.jboss.org/browse/ERT-693
> Project: Eclipse Release Train
…
[View More]> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Created attachment 276946
> Wizard screenshot on Eclipse 4.10
> Swithcing from Eclipse 4.9 platform to Eclipse 4.10. The size computations for various of our 'pull down' style text combo widgets are now wrong. They result in text being cut-off and in some cases totally unreadable (if the text is just one character, cutting of any part of the text will do that).
> One of my coleagues tried the wizard on Mac and it looks fine there. So this looks to be a regression in Linux SWT only.
> I'm attaching two screenshots, one from before Eclipse 4.9 and one from Eclipse 4.10.
> This doesn't appear to affect all combo boxes. Some boxes are drawn correctly. I think it has something to do with the fact that the affected boxes are not on screen when the wizard is initially shown. These widgets are added later on (dynamically populated from data read from a web service) and so there are some calls being made to 'reflow/relayout' the page after the widgets have been added or their contents changed somehow.
> In fact with the wizard from which these screenshots here are taken, the widgets briefly appear on screen 'correctly' (a bit hard to be sure, as they only appear very briefly) and then they get resized to a smaller size cutting of the contents.
> When sized correctly (E 4.9) the widget's width takes into account all of these:
> 1) text in the widget currently visible on screen
> 2) the width of the little pull-down arrow.
> 3) text in the pull-down menu (i.e. the other items that can be chosen by the user could be wider, and the widget acomodates enough space to show the largest of them).
> When sized 'incorrectly' (E 4.10) what it looks like to me is that instead only the currently visible text is taken into account. It does not account for the other items in the list, nor the width of the pull-down icon.
> I'll see if I can come up with some code snippet to reproduce this problem, and, if able to, will attach it later.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months
[JBoss JIRA] (JBIDE-26460) Cannot start CDK/Openshift with Oracle JDK 11.0.1
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26460?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-26460.
---------------------------------
Verified on 12.10.0.AM1-v20181219-0437-B3704.
> Cannot start CDK/Openshift with Oracle JDK 11.0.1
> -------------------------------------------------
>
> Key: JBIDE-26460
> URL: https://issues.jboss.org/browse/JBIDE-26460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
…
[View More]> Components: cdk, openshift
> Affects Versions: 4.10.0.AM1
> Environment: Fedora 28, Java 11 (oracle's JDK 11.0.1)
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.11.0.AM1
>
> Attachments: Screenshot_20181029_171905.png
>
>
> While starting CDK 3.6.0, I get an error while creating openshift connection.
> {code}
> eclipse.buildId=12.10.0.AM1-v20181026-0745-B3616
> java.version=11.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.core.jobs
> Error
> Mon Oct 29 17:00:57 CET 2018
> An internal error occurred during: "Inspecting CDK environment...".
> java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter
> at com.openshift.restclient.utils.Base64Coder.encode(Base64Coder.java:43)
> at com.openshift.restclient.utils.Base64Coder.encode(Base64Coder.java:55)
> at com.openshift.internal.restclient.okhttp.BasicChallangeHandler.handleChallange(BasicChallangeHandler.java:47)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator$1.authenticate(OpenShiftAuthenticator.java:91)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.java:294)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:160)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
> at okhttp3.RealCall.execute(RealCall.java:77)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:97)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:59)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.java:294)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:160)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
> at okhttp3.RealCall.execute(RealCall.java:77)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:298)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:274)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:238)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:219)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:400)
> at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.internal.cdk.server.core.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:115)
> at org.jboss.tools.openshift.internal.cdk.server.core.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:73)
> at org.jboss.tools.openshift.internal.cdk.server.core.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:60)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter cannot be found by org.jboss.tools.openshift.client_3.6.0.AM1-v20181026-0330-B4105
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 36 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months
[JBoss JIRA] (JBIDE-26506) Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26506?page=com.atlassian.jira.plugi... ]
Ondrej Dockal reassigned JBIDE-26506:
-------------------------------------
Assignee: Jeff MAURY
> Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26506
> URL: https://issues.jboss.org/browse/…
[View More]JBIDE-26506
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.11.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.11.x
>
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
> Missing requirement: Model 4.2.0.Final (org.jboss.tools.windup.model 4.2.0.Final) requires 'osgi.bundle; org.eclipse.emf.transaction 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
> To: org.eclipse.equinox.p2.iu; org.jboss.tools.windup.model [4.2.0.Final,4.2.0.Final]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months
[JBoss JIRA] (JBIDE-26479) Missing connector to Red Hat Application Migration Toolkit
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26479?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-26479.
---------------------------------
Connector is available, though, we have to open new jira (JBIDE-26506) as there is remediation page. Closing this one.
> Missing connector to Red Hat Application Migration Toolkit
> ----------------------------------------------------------
>
> Key: JBIDE-26479
> URL: https://issues.jboss.org/…
[View More]browse/JBIDE-26479
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.11.0.AM1
>
> Attachments: Screenshot_20181204_085116.png
>
>
> There is missing central connector to RH Application Migration Tool Kit. Happened when one tries to install this app from central into latest devstudio.
> Error log:
> {code}
> eclipse.buildId=12.10.0.AM1-v20181129-0845-B3670
> java.version=1.8.0_191
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.discovery.core
> Error
> Tue Dec 04 08:58:44 CET 2018
> Problems occurred while performing installation: The following connectors are not available: Red Hat Application Migration Toolkit (id=org.jboss.tools.windup.feature.feature.group, site=http://download.jboss.org/jbosstools/photon/stable/updates/rhamt/)
> org.eclipse.core.runtime.CoreException: The following connectors are not available: Red Hat Application Migration Toolkit (id=org.jboss.tools.windup.feature.feature.group, site=http://download.jboss.org/jbosstools/photon/stable/updates/rhamt/)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.checkForUnavailable(PrepareInstallProfileJob.java:374)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.computeInstallableUnits(PrepareInstallProfileJob.java:284)
> at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:116)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months
[JBoss JIRA] (JBIDE-26506) Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26506?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26506:
----------------------------------
Fix Version/s: 4.11.x
> Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26506
> URL: https://issues.jboss.org/browse/JBIDE-…
[View More]26506
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.11.0.AM1
> Reporter: Ondrej Dockal
> Priority: Major
> Fix For: 4.11.x
>
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
> Missing requirement: Model 4.2.0.Final (org.jboss.tools.windup.model 4.2.0.Final) requires 'osgi.bundle; org.eclipse.emf.transaction 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
> To: org.eclipse.equinox.p2.iu; org.jboss.tools.windup.model [4.2.0.Final,4.2.0.Final]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months
[JBoss JIRA] (JBIDE-26506) Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-26506:
-------------------------------------
Summary: Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
Key: JBIDE-26506
URL: https://issues.jboss.org/browse/JBIDE-26506
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, central-update
Affects Versions: 4.11.0.AM1
Reporter: Ondrej Dockal
{code}
Cannot …
[View More]complete the install because one or more required items could not be found.
Software being installed: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
Missing requirement: Model 4.2.0.Final (org.jboss.tools.windup.model 4.2.0.Final) requires 'osgi.bundle; org.eclipse.emf.transaction 0.0.0' but it could not be found
Cannot satisfy dependency:
From: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
To: org.eclipse.equinox.p2.iu; org.jboss.tools.windup.model [4.2.0.Final,4.2.0.Final]
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 3 months