[JBoss JIRA] (JBIDE-21818) Too large margins in wizards
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21818 at 3/4/16 3:41 PM:
-----------------------------------------------------------------------
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method have first line like
{code}
GridLayoutFactory.fillDefaults().margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worse on another. Then, could it be better just to stick to default 5 for margin in all wizards?
And, AbstractOpenShiftWizardPage itself in createControl() creates container with margin 6, and then its child, which becomes parent for doCreateControls and gets its margin 10, which makes total of 16.
was (Author: scabanovich):
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method have first line like
{code}
GridLayoutFactory.fillDefaults().margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worse on another. Then, could it be better just to stick to default 5 for margin in all wizards?
> Too large margins in wizards
> ----------------------------
>
> Key: JBIDE-21818
> URL: https://issues.jboss.org/browse/JBIDE-21818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2016-03-04 11.19.59.png
>
>
> Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general.
> See attached screenshot as an example
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21818) Too large margins in wizards
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21818 at 3/4/16 3:27 PM:
-----------------------------------------------------------------------
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method have first line like
{code}
GridLayoutFactory.fillDefaults().margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worse on another. Then, could it be better just to stick to default 5 for margin in all wizards?
was (Author: scabanovich):
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method have first line like
{code}
GridLayoutFactory.fillDefaults().margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worth on another. Then, could it be better just to stick to default 5 for margin in all wizards?
> Too large margins in wizards
> ----------------------------
>
> Key: JBIDE-21818
> URL: https://issues.jboss.org/browse/JBIDE-21818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2016-03-04 11.19.59.png
>
>
> Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general.
> See attached screenshot as an example
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21818) Too large margins in wizards
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21818 at 3/4/16 3:25 PM:
-----------------------------------------------------------------------
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method have first line like
{code}
GridLayoutFactory.fillDefaults().margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worth on another. Then, could it be better just to stick to default 5 for margin in all wizards?
was (Author: scabanovich):
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method has first line like
{code}
GridLayoutFactory.fillDefaults().numColumns(3).margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worth on another. Then, could it be better just to stick to default 5 for margin in all wizards?
> Too large margins in wizards
> ----------------------------
>
> Key: JBIDE-21818
> URL: https://issues.jboss.org/browse/JBIDE-21818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2016-03-04 11.19.59.png
>
>
> Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general.
> See attached screenshot as an example
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21818) Too large margins in wizards
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21818:
-----------------------------------------------
Many wizard pages inherited from AbstractOpenShiftWizardPage, in doCreateControls method has first line like
{code}
GridLayoutFactory.fillDefaults().numColumns(3).margins(10, 10).applyTo(parent);
{code}
that sets margin 10 (default is 5) in most pages, in some 6, in some 1. Evidently, it looks differently on different OS. I do see on the screenshot attached that margins are too large, but when I look at the same page in my Ubuntu, it does not causes that feeling, though comparing to other Eclipse wizards, the margin is larger. So, if adjusted to look perfect on one OS, it can look worth on another. Then, could it be better just to stick to default 5 for margin in all wizards?
> Too large margins in wizards
> ----------------------------
>
> Key: JBIDE-21818
> URL: https://issues.jboss.org/browse/JBIDE-21818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2016-03-04 11.19.59.png
>
>
> Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general.
> See attached screenshot as an example
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21817) Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21817?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21817 at 3/4/16 3:14 PM:
-----------------------------------------------------------------------
That is purely UI lock. 1. Workbench window loads. 2. Editor loads and makes loading window wait. 3. Editor starts modal dialog and waits. 4. Dialog asks permission to run a task in ui thread. It might be too much for thread manager to handle. So that the permission is not granted - lock. But there remains one part of UI active - stop button.
I do remember such cases in the long past, when an editor could be opened successfully manually, but if left active at closing Eclipse it caused deadlock at the next start of Eclipse at auto loading the editor.
was (Author: scabanovich):
That is purely UI lock. 1. Workbench window loads. 2. Editor loads and makes loading window wait. 3. Editor starts modal dialog and waits. 4. Dialog asks permission to run in ui thread. It might be too much for thread manager to handle. So that the permission is not granted - lock. But there remains one part of UI active - stop button.
I do remember such cases in the long past, when an editor could be opened successfully manually, but if left active at closing Eclipse it caused deadlock at the next start of Eclipse at auto loading the editor.
> Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21817
> URL: https://issues.jboss.org/browse/JBIDE-21817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: jstack.txt, LockAtStart.png
>
>
> 1. Close Eclipse with
> - Server Editor for OpenShift 2 server adapter open;
> - password for an Opebshift 2 connection not saved in the secure storage;
> - OpenShift Explorer active (maybe not important).
> 2. Open Eclipse - Sign In to OpenShift wizard appears while the application window remains only partially loaded (see screenshot). Once this is reproduced, it is reproduced at each Eclipse start.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs are locked.
> 5. Only red button cancelling connection is active, press it, wizard is unlocked (null pointer exception is fixed in JBIDE-21707).
> 6. Press Cancel, wizard is closed, Application window completes loading. - That
> 7. Connection may be established by Refresh action.
> Stack trace that calls Sign In to Openshift wizard before main window is loaded, it shows that call is initiated by loading Server Editor:
> {code}
> Thread [main] (Suspended (breakpoint at line 274 in Window))
> WizardDialog(Window).<init>(IShellProvider) line: 274
> WizardDialog(Dialog).<init>(IShellProvider) line: 438
> WizardDialog(Dialog).<init>(Shell) line: 419
> WizardDialog(TrayDialog).<init>(Shell) line: 138
> WizardDialog(TitleAreaDialog).<init>(Shell) line: 130
> WizardDialog.<init>(Shell, IWizard) line: 308
> WizardUtils.openWizardDialog(IWizard, Shell) line: 242
> CredentialsPrompter$1.run() line: 44
> UISynchronizer(Synchronizer).syncExec(Runnable) line: 186
> UISynchronizer.syncExec(Runnable) line: 145
> Display.syncExec(Runnable) line: 4634
> CredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 33
> LazyCredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 39
> ExpressConnection.promptForCredentials() line: 284
> ExpressConnection.createUser() line: 218
> ExpressConnection.connect() line: 198
> ExpressServerUtils.getApplication(IServerAttributes) line: 161
> ExpressServerUtils.getDeployFolder(IServerAttributes) line: 251
> ExpressServerEditorSection.initWidgets() line: 117
> ExpressServerEditorSection.createSection(Composite) line: 100
> OverviewEditorPart(ServerEditorPart).insertSections(Composite, String) line: 327
> OverviewEditorPart.createPartControl(Composite) line: 279
> ServerEditor(MultiPageEditorPart).addPage(int, IEditorPart, IEditorInput) line: 244
> ServerEditor(MultiPageEditorPart).addPage(IEditorPart, IEditorInput) line: 214
> ServerEditor.createPages() line: 247
> ServerEditor(MultiPageEditorPart).createPartControl(Composite) line: 363
> CompatibilityEditor(CompatibilityPart).createPartControl(IWorkbenchPart, Composite) line: 151
> CompatibilityEditor.createPartControl(IWorkbenchPart, Composite) line: 99
> CompatibilityEditor(CompatibilityPart).create() line: 341
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> MethodRequestor.execute() line: 56
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 925
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 906
> InjectorImpl.inject(Object, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 148
> InjectorImpl.internalMake(Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 372
> InjectorImpl.make(Class<T>, PrimaryObjectSupplier) line: 291
> ContextInjectionFactory.make(Class<T>, IEclipseContext) line: 162
> ReflectionContributionFactory.createFromBundle(Bundle, IEclipseContext, IEclipseContext, URI) line: 105
> ReflectionContributionFactory.doCreate(String, IEclipseContext, IEclipseContext) line: 74
> ReflectionContributionFactory.create(String, IEclipseContext) line: 56
> ContributedPartRenderer.createWidget(MUIElement, Object) line: 129
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> StackRenderer.showTab(MUIElement) line: 1306
> StackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> AreaRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine$1.run() line: 537
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement, Object, IEclipseContext) line: 521
> ElementReferenceRenderer.createWidget(MUIElement, Object) line: 70
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PerspectiveRenderer.processContents(MElementContainer<MUIElement>) line: 49
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveStackRenderer.showTab(MUIElement) line: 82
> PerspectiveStackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PerspectiveStackRenderer.postProcess(MUIElement) line: 63
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> WBWRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> WBWRenderer.processContents(MElementContainer<MUIElement>) line: 614
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PartRenderingEngine$4.run() line: 1066
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1023
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 651
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 595
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21817) Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21817?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21817 at 3/4/16 3:05 PM:
-----------------------------------------------------------------------
That is purely UI lock. 1. Workbench window loads. 2. Editor loads and makes loading window wait. 3. Editor starts modal dialog and waits. 4. Dialog asks permission to run in ui thread. It might be too much for thread manager to handle. So that the permission is not granted - lock. But there remains one part of UI active - stop button.
I do remember such cases in the long past, when an editor could be opened successfully manually, but if left active at closing Eclipse it caused deadlock at the next start of Eclipse at auto loading the editor.
was (Author: scabanovich):
That is purely UI lock. 1. Workbench window loads. 2. Editor loads and makes loading window wait. 3. Editor starts modal dialog and waits. 4. Dialog asks permission to run in ui thread. It might be too much for thread manager to handle. So that the permission is not granted - lock. But there remains one part of UI active - stop button.
> Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21817
> URL: https://issues.jboss.org/browse/JBIDE-21817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: jstack.txt, LockAtStart.png
>
>
> 1. Close Eclipse with
> - Server Editor for OpenShift 2 server adapter open;
> - password for an Opebshift 2 connection not saved in the secure storage;
> - OpenShift Explorer active (maybe not important).
> 2. Open Eclipse - Sign In to OpenShift wizard appears while the application window remains only partially loaded (see screenshot). Once this is reproduced, it is reproduced at each Eclipse start.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs are locked.
> 5. Only red button cancelling connection is active, press it, wizard is unlocked (null pointer exception is fixed in JBIDE-21707).
> 6. Press Cancel, wizard is closed, Application window completes loading. - That
> 7. Connection may be established by Refresh action.
> Stack trace that calls Sign In to Openshift wizard before main window is loaded, it shows that call is initiated by loading Server Editor:
> {code}
> Thread [main] (Suspended (breakpoint at line 274 in Window))
> WizardDialog(Window).<init>(IShellProvider) line: 274
> WizardDialog(Dialog).<init>(IShellProvider) line: 438
> WizardDialog(Dialog).<init>(Shell) line: 419
> WizardDialog(TrayDialog).<init>(Shell) line: 138
> WizardDialog(TitleAreaDialog).<init>(Shell) line: 130
> WizardDialog.<init>(Shell, IWizard) line: 308
> WizardUtils.openWizardDialog(IWizard, Shell) line: 242
> CredentialsPrompter$1.run() line: 44
> UISynchronizer(Synchronizer).syncExec(Runnable) line: 186
> UISynchronizer.syncExec(Runnable) line: 145
> Display.syncExec(Runnable) line: 4634
> CredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 33
> LazyCredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 39
> ExpressConnection.promptForCredentials() line: 284
> ExpressConnection.createUser() line: 218
> ExpressConnection.connect() line: 198
> ExpressServerUtils.getApplication(IServerAttributes) line: 161
> ExpressServerUtils.getDeployFolder(IServerAttributes) line: 251
> ExpressServerEditorSection.initWidgets() line: 117
> ExpressServerEditorSection.createSection(Composite) line: 100
> OverviewEditorPart(ServerEditorPart).insertSections(Composite, String) line: 327
> OverviewEditorPart.createPartControl(Composite) line: 279
> ServerEditor(MultiPageEditorPart).addPage(int, IEditorPart, IEditorInput) line: 244
> ServerEditor(MultiPageEditorPart).addPage(IEditorPart, IEditorInput) line: 214
> ServerEditor.createPages() line: 247
> ServerEditor(MultiPageEditorPart).createPartControl(Composite) line: 363
> CompatibilityEditor(CompatibilityPart).createPartControl(IWorkbenchPart, Composite) line: 151
> CompatibilityEditor.createPartControl(IWorkbenchPart, Composite) line: 99
> CompatibilityEditor(CompatibilityPart).create() line: 341
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> MethodRequestor.execute() line: 56
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 925
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 906
> InjectorImpl.inject(Object, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 148
> InjectorImpl.internalMake(Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 372
> InjectorImpl.make(Class<T>, PrimaryObjectSupplier) line: 291
> ContextInjectionFactory.make(Class<T>, IEclipseContext) line: 162
> ReflectionContributionFactory.createFromBundle(Bundle, IEclipseContext, IEclipseContext, URI) line: 105
> ReflectionContributionFactory.doCreate(String, IEclipseContext, IEclipseContext) line: 74
> ReflectionContributionFactory.create(String, IEclipseContext) line: 56
> ContributedPartRenderer.createWidget(MUIElement, Object) line: 129
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> StackRenderer.showTab(MUIElement) line: 1306
> StackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> AreaRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine$1.run() line: 537
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement, Object, IEclipseContext) line: 521
> ElementReferenceRenderer.createWidget(MUIElement, Object) line: 70
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PerspectiveRenderer.processContents(MElementContainer<MUIElement>) line: 49
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveStackRenderer.showTab(MUIElement) line: 82
> PerspectiveStackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PerspectiveStackRenderer.postProcess(MUIElement) line: 63
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> WBWRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> WBWRenderer.processContents(MElementContainer<MUIElement>) line: 614
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PartRenderingEngine$4.run() line: 1066
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1023
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 651
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 595
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> {code}
--
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 commented on JBIDE-21816:
------------------------------------------
[~snjeza] I have fc23/GTK 3.18 and I never experienced JBIDE-21038.
> 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-21817) Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21817?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21817:
-----------------------------------------------
That is purely UI lock. 1. Workbench window loads. 2. Editor loads and makes loading window wait. 3. Editor starts modal dialog and waits. 4. Dialog asks permission to run in ui thread. It might be too much for thread manager to handle. So that the permission is not granted - lock. But there remains one part of UI active - stop button.
> Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21817
> URL: https://issues.jboss.org/browse/JBIDE-21817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: jstack.txt, LockAtStart.png
>
>
> 1. Close Eclipse with
> - Server Editor for OpenShift 2 server adapter open;
> - password for an Opebshift 2 connection not saved in the secure storage;
> - OpenShift Explorer active (maybe not important).
> 2. Open Eclipse - Sign In to OpenShift wizard appears while the application window remains only partially loaded (see screenshot). Once this is reproduced, it is reproduced at each Eclipse start.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs are locked.
> 5. Only red button cancelling connection is active, press it, wizard is unlocked (null pointer exception is fixed in JBIDE-21707).
> 6. Press Cancel, wizard is closed, Application window completes loading. - That
> 7. Connection may be established by Refresh action.
> Stack trace that calls Sign In to Openshift wizard before main window is loaded, it shows that call is initiated by loading Server Editor:
> {code}
> Thread [main] (Suspended (breakpoint at line 274 in Window))
> WizardDialog(Window).<init>(IShellProvider) line: 274
> WizardDialog(Dialog).<init>(IShellProvider) line: 438
> WizardDialog(Dialog).<init>(Shell) line: 419
> WizardDialog(TrayDialog).<init>(Shell) line: 138
> WizardDialog(TitleAreaDialog).<init>(Shell) line: 130
> WizardDialog.<init>(Shell, IWizard) line: 308
> WizardUtils.openWizardDialog(IWizard, Shell) line: 242
> CredentialsPrompter$1.run() line: 44
> UISynchronizer(Synchronizer).syncExec(Runnable) line: 186
> UISynchronizer.syncExec(Runnable) line: 145
> Display.syncExec(Runnable) line: 4634
> CredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 33
> LazyCredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 39
> ExpressConnection.promptForCredentials() line: 284
> ExpressConnection.createUser() line: 218
> ExpressConnection.connect() line: 198
> ExpressServerUtils.getApplication(IServerAttributes) line: 161
> ExpressServerUtils.getDeployFolder(IServerAttributes) line: 251
> ExpressServerEditorSection.initWidgets() line: 117
> ExpressServerEditorSection.createSection(Composite) line: 100
> OverviewEditorPart(ServerEditorPart).insertSections(Composite, String) line: 327
> OverviewEditorPart.createPartControl(Composite) line: 279
> ServerEditor(MultiPageEditorPart).addPage(int, IEditorPart, IEditorInput) line: 244
> ServerEditor(MultiPageEditorPart).addPage(IEditorPart, IEditorInput) line: 214
> ServerEditor.createPages() line: 247
> ServerEditor(MultiPageEditorPart).createPartControl(Composite) line: 363
> CompatibilityEditor(CompatibilityPart).createPartControl(IWorkbenchPart, Composite) line: 151
> CompatibilityEditor.createPartControl(IWorkbenchPart, Composite) line: 99
> CompatibilityEditor(CompatibilityPart).create() line: 341
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> MethodRequestor.execute() line: 56
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 925
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 906
> InjectorImpl.inject(Object, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 148
> InjectorImpl.internalMake(Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 372
> InjectorImpl.make(Class<T>, PrimaryObjectSupplier) line: 291
> ContextInjectionFactory.make(Class<T>, IEclipseContext) line: 162
> ReflectionContributionFactory.createFromBundle(Bundle, IEclipseContext, IEclipseContext, URI) line: 105
> ReflectionContributionFactory.doCreate(String, IEclipseContext, IEclipseContext) line: 74
> ReflectionContributionFactory.create(String, IEclipseContext) line: 56
> ContributedPartRenderer.createWidget(MUIElement, Object) line: 129
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> StackRenderer.showTab(MUIElement) line: 1306
> StackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> AreaRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine$1.run() line: 537
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement, Object, IEclipseContext) line: 521
> ElementReferenceRenderer.createWidget(MUIElement, Object) line: 70
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PerspectiveRenderer.processContents(MElementContainer<MUIElement>) line: 49
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveStackRenderer.showTab(MUIElement) line: 82
> PerspectiveStackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PerspectiveStackRenderer.postProcess(MUIElement) line: 63
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> WBWRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> WBWRenderer.processContents(MElementContainer<MUIElement>) line: 614
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PartRenderingEngine$4.run() line: 1066
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1023
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 651
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 595
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> {code}
--
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 commented on JBIDE-21816:
------------------------------------------
[~scabanovich] Reading you this seems to affect GTK 3.10 only. The weird part then is that [~snjeza] couldnt reproduce it in this version. Maybe this is Ubuntu only? [~snjeza] What Linux distro are you using with 3.10?
I get more and more the impression that we should leave this as is, not adding a weird (but apparently effective) workaround. If this really is Ubuntu/GTK 3.10 (a quite old GTK3 version) chances are very small that significant part of our users are affected.
> 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