Community
Participate
Working Groups
Build Identifier: I20100608-0911 In our application, we have a perspective which has an upper folder and a lower folder of views. The upper folder holds multiple master views showing overviews of different business objects. The lower folder holds the corresponding details views showing the details of the business object select in the currently active master view. If such a master view is selected by the user, it refreshes itself (i.e. the contents of the overview table) and also resets the selection in the table. This also causes a refresh of the according details view. In our application, only one details view is visible at a time, but I left that out in the sample plugin attached to this bug. Thus, all details views are visible all the time. Refreshing a details view also brings it to front using ...getActivePage().showView(viewId). This call seems to cause another partVisible event for the master view, although this event is already being processed. The attached sample application has four views: Two master views in the top folder, and two details views in the bottom folder. On activating MasterViewTwo, it activates DetailsViewTwo. This causes another partVisible event for MasterViewTwo. Reproducible: Always Steps to Reproduce: 1. Load the sample application into a eclipse 3.6 workspace and run it 2. Click on "Master2" 3. The console output shows that the partVisible event is processed twice for the MasterViewTwo. Note that this only happens the first time you click on "Master2" after you start the application. If you click on "Master1" and "Master2" again, partVisible is fired only once. As workaround, we have to remember that we are already processing partVisible and ignore the second call :-(
Maybe it's connected with #318131
Created attachment 175067 [details] Sample application to show the events
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
