Community
Participate
Working Groups
The new maximize behavior is very nice that everything goes into a dock/fastview (so that i can now switch editors or have 2 editors at the same time in a maximize state) But my package explorer/navigator view goes to the left size. I don't want that because i don't have a quick dock there yet and then everything must be resized because suddenly there must be space made to that side to have the dock. So i select those and say: Dock On->Bottom. It then goes to the bottom where i want it. But after i restore anything and again maximize a editor. it is again on the left side. But the last time i did say that i want to have it on the bottom. It would be nice if that is remembered.
this is almost fixed in the ibuild: I20061102-0010 it does remember it now for one run. Only if i restart eclipse it is again on the left side instead of bottom. So now only remember this "minimize" persistent and this bug can be closed :)
Thanks Johan, I'll add it to the list of 'must fix' defects for the work item...
Fixed as of >20070228....
Verified in 20070321-0010.
i just tested this in the 3.3M6 build: I20070323-1616 And it still doesn't remember the position at my place I minimize for example the package explorer/resource navigator view parts. That goes to the left side of the window. But that distorts everything (resizes/layouts parts because it must make space) and i don't want that so i drag the dock down. Then i maximize it again it and minimize it again. And yes it goes to the dock at the bottom. Then i maximize it again and restart eclipse. After the restart it minimize the same view again and it goes again to the left side where i don't want any docks.
Let me re-check...
Johan, my apologies...it does indeed fail for the case you mention...
*** Bug 181037 has been marked as a duplicate of this bug. ***
*** Bug 183523 has been marked as a duplicate of this bug. ***
Committed in >20070426. The TrimLayout now saves the cached info and the FastViewManager correctly uses this info to create the trim in its cached location (if any).
Using build i0501-0010 this happens again. On restart the minimize view wasn't in the correct location. Will try and find steps...
Verified in I20070501-0010.
Should already have been marked as fixed...
Now verified in I20070501-0010.
Eric, I reopened this because it happened to me again with that build.
Leave this open, in case someone can find a pattern. Eric and I have been unable to duplicate this (at all). For anyone who is seeing it, please attempt to repeatable steps, since we're unlikely to be able to fix it otherwise.
Happened again to me with build I20070503-1400.
DJ, when I came over you were unable to repro this...do you have a -repeatable- set of steps that exhibit this behavior ?
Not yet. It just happened when I started this morning. (note I had already started that workspace with that build before)
Note that this happens quite frequently to me with the latest builds. I'm not sure what repeatable steps to look for since I just shutdown and then start Eclipse and its there.
I'm gonna have to install a camera in your office...;-).
Can't repro and nobody else has reported it...
