Community
Participate
Working Groups
I have an application that is using multiple instances of a single view description. These instances override #init(IViewSite) and using the secondary identifier in the view site, they update the title of the view to match. From the perspective of the title in the view tabs, this seems to work fine. Unfortunately, the CyclePartAction does not seem to pick this up in the same way. The CyclePartAction will display the default view title for all of the views that have not been made visible yet. These views have not had a call to #init(IViewSite) and have not yet been able to update the title of the view. I'm not sure where the tab title comes from in this case, but it is correct while the CyclePartAction still shows the default title. I would expect (and really need) them to display the same value. Once the view has been actually displayed, the CyclePartAction will show the correct value. I'm attaching two screenshots to the bug report. The "incorrect" snapshot shows the state before bringing the view to the top in which the title tab value is correct, but the cycle dialog is not. The "correct" snapshot shows that after bringing the second view to the top, the cycle dialog now correctly matches the title on the view's tab.
Created attachment 31962 [details] Mismatch between view title tab and cycle dialog
Created attachment 31963 [details] Correct matching title between view title tab and cycle dialog
Is this still a problem in 3.3? PW
I'm no longer working on the product that had this problem. I'm not sure if it is still a problem in 3.3.
Still need to test. PW
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.
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.
