Community
Participate
Working Groups
Build ID: M20080911-1700 Steps To Reproduce: 1. Create an RCP that allows opening of files outside of the workspace via command line arguments. 2. Start with a brand new workspace, clean configuration. 3. Use command line arg to point to a file to be opened. 4. RCP will open the file in a editor, however the user will still see the welcome page which takes up the entire workspace. 5. When user closes the welcome page, they will see that the editor does not fill up the entire workspace area that the editor should be occupying. Perhaps because the welcome page is being displayed, the size calculations are not correct for editors? More information:
Patrick, could you please attach a screen shot showing the result after closing the Intro?
Created attachment 124190 [details] Application opened with welcome page - file has been loaded in background.
Created attachment 124191 [details] After closing welcome page
What happens when you resize the window when it's in this state? Does the editor expand to take up all the space then? How about on the second restart (i.e. when the intro doesn't come up?
Resizing the window does not cause the editor to resize at all in this state. However, minimizing the editor (not the window) and then restoring it again will cause it to begin behaving correctly.
Patrick, is there a chance that you could provide a 'stub' RCP app that shows the effect? Something really simple (i.e. uses the text editor...) would really help us in tracking this down (this is a code flow we hadn't anticipated). Also, you can likely mitigate this (for now) by setting the Intro view into 'standby' state before opening the editor. This will place the Intro view (un-maximized) to the right of the editor area...the code below should work to do this... IIntroManager im = PlatformUI.getWorkbench().getIntroManager(); if (im != null) { im.setIntroStandby(im.getIntro(), true);
Thanks guys, Your workaround solved the problem for me. I will try to find some time to whip up a stub app. We're in a busy time period right now so it might take awhile...
Thanks Patrick, we all know the feeling...;-).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
