Community
Participate
Working Groups
The fix for bug 65835 added code that passes an Integer into StackPresentation.add. This code works for DefaultStackPresentation, but will cause a ClassCastException for a presentation that uses a different cookie type (for example, an MDI-style presentation would be likely to use Points or Rectangles). The second argument to addPart may only be an object that the StackPresentation itself returned in a StackDropResult or null. The workbench indicates the order of views in the perspective by the order of calls to addPart. If DefaultPartPresentation chooses not to honor that order, this is either a bug in DefaultPartPresentation or an intentional design decision. However, it is not the responsibility of the workbench to work around bugs in particular presentations.
Note that this breaks bug 65835. The workbench is now overriding the tab order by making assumptions about the way DefaultStackPresentation interprets drag/drop cookies.
Correction to comment 1: this breaks bug 62038, not bug 65835.
stefan, do you think this is critical for 3.0.1? do you have a fix for this?
I shouldn't have flagged as major: presentations can workaround this by checking if cookie instanceof Integer at the start of their add method.
Reassigning the last of Stefan's bugs.
Paul is this obsolete?
Is this still a problem in 3.3? PW
Changes requested on bug 193523
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.