Bugzilla – Full Text Bug Listing
| Summary: | [ViewMgmt] Eclipse 3.5.1 destroys editor titles... | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Daniel Stein <daniel.stein> | ||||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Remy Suen <remy.suen> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | darin.eclipse, emoffatt, prakash, remy.suen | ||||||
| Version: | 3.5.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Daniel Stein
(In reply to comment #0) > (see attached screenshot:) No screenshot has been attached. Which service pack are you running on? Created attachment 160471 [details]
the mentioned screenshot
Thanks. We are using Eclipse SDK Version: 3.5.1 (In reply to comment #2) > Created an attachment (id=160471) [details] > the mentioned screenshot Does the error occur on XP style instead of Win2k/Classic style? (In reply to comment #3) > We are using Eclipse SDK Version: 3.5.1 I was referring to your Microsoft Windows XP service pack actually. (In reply to comment #4) > (In reply to comment #2) > > Created an attachment (id=160471) [details] [details] > > the mentioned screenshot > > Does the error occur on XP style instead of Win2k/Classic style? > > (In reply to comment #3) > > We are using Eclipse SDK Version: 3.5.1 > > I was referring to your Microsoft Windows XP service pack actually. Our Pc's uses Win XP Service Pack 2 (In reply to comment #2) > Created an attachment (id=160471) [details] [details] > the mentioned screenshot Does the error occur on XP style instead of Win2k/Classic style? (In reply to comment #6) > Does the error occur on XP style instead of Win2k/Classic style? What does this mean? How can I change this style? Thank you so much for your interest and help. This problems drives me crazy :-) Daniel, this appears to be a layout issue (i.e. some toolbar is being incorrectly placed on top of the editor's tab)... Does a resize of the workbench window solve the issue? What happens when you open another editor? Do you use the single editor tab preference? (In reply to comment #8) Thanks for your reply. > Does a resize of the workbench window solve the issue? No. Opening the view the buttons belong to fix the problem. > What happens when you open another editor? The "defect editor" remains in the same state. The new opened editor shows up normaly. > Do you use the single editor tab preference? I don't know. Do you mean this preference? : IWorkbenchPreferenceConstants#IWorkbenchPreferenceConstants
> IWorkbenchPreferenceConstants#IWorkbenchPreferenceConstants
Uups, pasting Error:
IWorkbenchPreferenceConstants#SHOW_MULTIPLE_EDITOR_TABS
Yes, but I think you already answered me indirectly when you said that the second editor opens 'normally' :). We're just trying to get a handle on where the problem might be. If it were a general issue we'd have been flooded with reports... Which view was it that supplied the TB you show in the screen cap? What was that view's current state in the UI (not there, in a stack but not on top, in the fast view bar...)? > Which view was it that supplied the TB you show in the screen cap? What was
> that view's current state in the UI (not there, in a stack but not on top, in
> the fast view bar...)?
I add a new screenshot (the defect window), that answers your questions. The View (title: Werte) contributes Actions to the Toolbar via
IToolBarManager toolbar = getViewSite().getActionBars().getToolBarManager();
toolbar.add(myAction)
...
Created attachment 164169 [details]
the defect window
Hi, I've got further information reagarding the described problem: In the view, which contains the buttons that overlays the "title-area" I set the background of the Toolbar to another color via the interface IToolbarManager2. The buttons in title-area now have the color that I set to the view-Toolbar-Manager. It seems that eclipse paints the view toolbar twice. One time in the view and one time in the editor title-area. The big question is why? (In reply to comment #7) > > Does the error occur on XP style instead of Win2k/Classic style? > > What does this mean? How can I change this style? If you access the properties of your desktop, you can change your theme. The Classic theme is the old flat theme whereas the XP theme is the new look that Microsoft gave to Windows in the XP release. (In reply to comment #15) > (In reply to comment #7) > > > Does the error occur on XP style instead of Win2k/Classic style? > > > > What does this mean? How can I change this style? > > If you access the properties of your desktop, you can change your theme. > > The Classic theme is the old flat theme whereas the XP theme is the new look > that Microsoft gave to Windows in the XP release. In my company we can't change the theme on our work machines. We must live with the old flat theme... If this problem still occurs on Eclipse 3.6.x, please provide code and steps to reproduce the problem. (In reply to comment #17) > If this problem still occurs on Eclipse 3.6.x, please provide code and steps to > reproduce the problem. The problem still occurs on Eclipse 3.6.1 but we finally found a workaround by chance: We changed the implementation of our EditorInput (IEditorInput) The method #exists() now returns true instead of false and we implemented the Interface IPersistableElement and return it in the Methode #getPersistable(). Finally we implemented an IElementFactory to recreate the editorInputs. Now the problem is gone. The advantage of the workaround is also that eclipse now recreates the editors that the user don't close on exit. But the wohle thing is very strange at all... From the screenshots, this bug feels similar to bug 329754. (In reply to comment #19) > From the screenshots, this bug feels similar to bug 329754. Thank you for the hint Daniel, just a heads up that I just committed a fix for bug 329754 and it may be worth checking once M6 comes out (or not if you're satisfied with your workaround). If you do could you please ping on this defect with your results ? (In reply to comment #21) > Daniel, just a heads up that I just committed a fix for bug 329754 and it may > be worth checking once M6 comes out (or not if you're satisfied with your > workaround). > > If you do could you please ping on this defect with your results ? Thanks for your work. I'll give M6 a try. (In reply to comment #22) > (In reply to comment #21) > > Daniel, just a heads up that I just committed a fix for bug 329754 and it may > > be worth checking once M6 comes out (or not if you're satisfied with your > > workaround). > > > > If you do could you please ping on this defect with your results ? > > Thanks for your work. I'll give M6 a try. Is there a chance to get the fix for 3.6 ? (In reply to comment #23) > Is there a chance to get the fix for 3.6 ? Very unlikely given the low severity of this problem (that being it does not cause Eclipse to crash or cause data loss for example). (In reply to comment #22) > (In reply to comment #21) > > Daniel, just a heads up that I just committed a fix for bug 329754 and it may > > be worth checking once M6 comes out (or not if you're satisfied with your > > workaround). > > > > If you do could you please ping on this defect with your results ? > > Thanks for your work. I'll give M6 a try. M6 fixed the problem. So I wait for 3.7 to come out and then migrate my app to it. Thanks! |