Community
Participate
Working Groups
Build Identifier: Build Identifier: 20090920-1017 Hello everyone: I filed a bug in the RAP bug list, but Ivan told me that the problem existed in the platform too,could you please have a look here? https://bugs.eclipse.org/bugs/show_bug.cgi?id=308079 Thanks a lot and Best Regards! Reproducible: Always Steps to Reproduce: 1.Start an rap service with the attached 4 bundles(https://bugs.eclipse.org/bugs/attachment.cgi?id=163807) 2.Start a new session. 3.Click "Open View 1" and "Open View 2" buttons on the toolbar to open these two view parts; 4.Close View2 and View1 in turn; 5.Click "Open View 3" and "Open View 1" buttons on the toolbar in turn; 6.View parts layout goes crazy~~~ Please check out the video(https://bugs.eclipse.org/bugs/attachment.cgi?id=163807) I uploaded for more detail. Thanks and Best Regards:) Tingel Christian
Video is here: https://bugs.eclipse.org/bugs/attachment.cgi?id=163806 sorry for any inconvenience. Thanks and Best Regards! Tingel Christian
Created attachment 164794 [details] 4 projects de-RAPed Launch a standard SDK app with -perspective viewlayouttester.perspective PW
The perspective is empty (except for the editor area set to visible=false). The 3 views are simply added using page.showView(*). If you add them all at once, they all show up in the same stack (good). If you open view 1 and 2, close 1 and 2, and then open 3, 2, 1: View 3 is on the left in a stack by itself, and view 1 and 2 are in the same stack (bad). But if I had to guess, this bug has probably been there for a long time... PW
Thanks Paul:) I agree with you, I used RAP 1.2 whose RCP counterpart is RCP 3.5. This bug has hidden itself for such a long time and I think it's might because there is seldom anyone using and orgnizing views in this way~~~ But it has really caused a lot of problems for me:( Thanks and Best Regards! Tingel Christian
Hi~ Can somebody please have a glance at this problem? Thanks and Best Regards! Tingel Christian
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.
