Bugzilla – Full Text Bug Listing
| Summary: | Blank Editor Screens after restart | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Céline Balouin <balouin.c> | ||||||
| Component: | RSE | Assignee: | dsdp.tm.rse-inbox <tm.rse-inbox> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | daniel_megert, jflicke, pwebster | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | other | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Céline Balouin
This multi-editor area on workspace restart issue looks like its the behavior of base eclipse. To reproduce, open two historic versions of a file in two text editors, drag one of them over so they are both visible, and then restart eclipse (In reply to comment #1) > This multi-editor area on workspace restart issue looks like its the behavior > of base eclipse. > > To reproduce, open two historic versions of a file in two text editors, drag > one of them over so they are both visible, and then restart eclipse This is not related to multi-editor area - it's the same if you only open one editor from the history (view) and restart. We do this is on purpose since such editors can have their data stored on far away servers and we don't want to contact them on restart. > 2.Open two different datasets in the editor What exactly does this step mean? Does it mean opening data from the history (view)? If so, is it CVS, Git, local or yet another kind of history? This bug comes from a customer of our eclipse based product. I believe it can be reproduced using any editors that have a non-persistable editor input, ie. return null from getPersistable(); These include opening local historic versions of a file in an editor, viewing a file from a team browser like cvs, and for our product opening a file from RSE, where we use editor inputs that are not persistable. If you have only editors open on non-persistable inputs, and you drag the editors around so that multiple are visible at once (ie. not stacked up behind each other), and restart the product, I don't know what the technical term is but there will be place holders for the locations of where the editors were, even though none of the editors will be reopened. I believe this request is that when restarting eclipse, if there is an area of the ide that was holding some editors, but non of those editors were persisted and re-opened, then that placeholder should be removed. I'll attach a picture of what i mean by "placeholder" If this is working as designed, we can forward that to our customer Created attachment 211284 [details]
Before Restart (4 historic versions)
Created attachment 211285 [details]
After Restart
Re: Open two different datasets in the editor A "dataset" is an IBM System z MVS "File". They are opened in our product using Remote Systems Explorer. We open these remote files using a non-persistable editor input so that when the product is restarted, any editors open on remote files will not be automatically re-opened. (In reply to comment #3) (In reply to comment #4) (In reply to comment #5) > I believe this request is that when restarting eclipse, if there is an area of > the ide that was holding some editors, but non of those editors were persisted > and re-opened, then that placeholder should be removed. > > I'll attach a picture of what i mean by "placeholder" > > If this is working as designed, we can forward that to our customer This is as designed. The user explicitly decided to have 4 editor areas. We would destroy this decision if we remove them on restart. If the bug is about this scenario, then it can be closed as INVALID. Ok... but i can see the customers point... if you end up in the situation with multiple empty editor areas after an eclipse restart, its a pain to reduce them back to one. The first time you open an editor, it shows up in one of the areas. Then you have to drag that editor onto an empty space to consolidate them, so its three drag actions. Having an empty editor area doesn't seem to be of any use. Any opened editors will all show up in just one of the areas, and to use any of the other areas you'd have to drag an editor over by hand. The empty areas don't seem to be of any use, they just take up real-estate. Jeremy, it looks like other people preferred to collapse those empty editor areas and hence we changed that behavior in 3.7 (see bug 110684). *** This bug has been marked as a duplicate of bug 110684 *** |