Community
Participate
Working Groups
Build Identifier: 20110615-0604 I have RCP program with a intro page. At first time, Indigo shows full intro page normally and then after about 5seconds it changed the layout. So it shows another views and editor. When I close some views and editor, then Indigo does not change layout. What Condition make Indigo change layout? Is there a way to fix this? Reproducible: Always
Please attach screenshots.
Created attachment 200963 [details] It is full page at the first time
Created attachment 200964 [details] after about 5 seconds Indigo changes layout
I'm not sure why that would be happening in your RCP App. Intro would only change from full screen to "standby" mode in response to a call to standbyStateChanged(). If you put a breakpoint in org.eclipse.ui.intro.config.CustomizableIntroPart.standbyStateChanged() it may give a clue as to what is happening to trigger this.
I have the same problem on 3.7.1 with my product. I'm under Linux, but I think other members of my team who are under Windows 7 also see this. This is with org.eclipse.ui.workbench_3.7.0.I20110519-0100.jar. I have put a breakpoint in CustomizableIntroPart.standbyStateChanged(). At some point it is called with its parameter standby set to true. Here it the relevant stack at that point: Thread [main] (Suspended (breakpoint at line 254 in CustomizableIntroPart)) CustomizableIntroPart.standbyStateChanged(boolean) line: 254 ViewIntroAdapterPart$2.run() line: 75 BusyIndicator.showWhile(Display, Runnable) line: 70 ViewIntroAdapterPart.setStandby(boolean) line: 71 ViewIntroAdapterPart$1.propertyChanged(Object, int) line: 56 ViewReference(WorkbenchPartReference).fireInternalPropertyChange(int) line: 375 ViewReference(WorkbenchPartReference).fireZoomChange() line: 540 ViewPane(PartPane).setZoomed(boolean) line: 356 ViewStack(PartStack).setZoomed(boolean) line: 1515 ViewSashContainer(PartSashContainer).zoomOut() line: 976 ViewSashContainer(PartSashContainer).childRequestZoomOut() line: 924 ViewStack(LayoutPart).requestZoomOut() line: 347 ViewStack(PartStack).setState(int) line: 1492 WorkbenchPage.setState(IWorkbenchPartReference, int) line: 4020 WorkbenchPage.toggleZoom(IWorkbenchPartReference) line: 4092 WorkbenchIntroManager.setIntroStandby(IIntroPart, boolean) line: 201 WorkbenchPage.checkIntro() line: 1198 WorkbenchPage.busyShowView(IViewPart, int) line: 1168 WorkbenchPage.busyShowView(String, String, int) line: 1140 WorkbenchPage$20.run() line: 3921 BusyIndicator.showWhile(Display, Runnable) line: 70 WorkbenchPage.showView(String, String, int) line: 3918 IDEWorkbenchPlugin$2.run() line: 382 In my case, it seems to be triggered by WorkbenchPage.busyShowView(IViewPart, int) where the IViewPart is org.eclipse.ui.internal.views.markers.ProblemsView and mode = 3. In the busyShowview method, checkIntro() is called, which decides to call intro.setIntroStandby(part, true) (here, part is the intro part). Until there's a fix, do you have an idea for a workaround?
On further investigation, this seems related to the Problems view. When I remove it from my default perspective, the bug is never triggered. It reappears as soon as I add it back. The fact that the bug only happens after a few seconds seems consistent with this as IDEWorkbecnhPlugin waits for PROBLEMS_VIEW_CREATION_DELAY = 6000ms before actually creating the view.
Any news on this issue, or idea for a workaround (which does not remove the 'Problems' view)?
(In reply to comment #7) > Any news on this issue, or idea for a workaround (which does not remove the > 'Problems' view)? No one is currently looking at this area. http://wiki.eclipse.org/Platform_UI/How_to_Contribute PW
Appears this was fixed in 3.8 PW *** This bug has been marked as a duplicate of bug 355560 ***
