Community
Participate
Working Groups
Created attachment 190986 [details] screen shot eclipse.buildId=I20110310-2200 I have a bunch of views stacked and attached to the bottom of my editor. There are really 2 separate issues: - When I maximize my editor they seem to be considered part of the editor and I still see them. - I am unable to minimize them. I've attached a screen shot of my perspective so you can see how I have things laid out.
(In reply to comment #0) > - When I maximize my editor they seem to be considered part of the editor and I > still see them. This is the expected behaviour because the stack is inside the shared area. You can see they are all visually within that "box" with one pair of min/max buttons. > - I am unable to minimize them. This is missing functionality.
(In reply to comment #1) > This is the expected behaviour because the stack is inside the shared area. You > can see they are all visually within that "box" with one pair of min/max > buttons. > Is it possible to lay out my views like in the attachment, but have only the editor show when I maximize it? (e.g. dock views below the editor and not be part of the shared area)
(In reply to comment #2) > Is it possible to lay out my views like in the attachment, but have only the > editor show when I maximize it? (e.g. dock views below the editor and not be > part of the shared area) Pretty sure no. Not unless you change the live model manually with Tom's tool or something. The DND is not flexible enough at the moment (also see bug 334278).
DJ, after a talk with Remy the root cause of your issue is that (as I understand) you didn't actually want to move the views *into* the shared area but rather to simply make the bottom stack occupy the same horizontal bounds as the editors. In 3.x the response to the drop operation was obvious in the sense that you couldn't *have* a view stack in the Editor Area. The defect is in the DnD implementation not being able to distinguish whether (when you split the shared area) you want the resulting stack inside or outside the area. This is but one of a number of issues related to exposing 4.x's new capabilities. Feedback is most welcome, drop by if you want...I'm getting a list of this type of issue together. Given your screen shot this is the expected behavior (except for not yet having a story for min/max *within* an area...).
I'm changing the defect's title to better reflect the work that will have to be done to address the root cause (ending up with the stack inside the shared area after the drop)... Tagging for M7 since we have to have a solution for this before release. I'll open a new defect to capture the more esoteric issue of how to handle min/max *within* an area...
This is working as of the last DnD update...
Verified in I20110604-2201
