Bug 110703 - [MPE] Dirty state in editor title not updated in MultiEditor
Summary: [MPE] Dirty state in editor title not updated in MultiEditor
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux-GTK
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-26 15:36 EDT by Douglas Pollock CLA
Modified: 2019-09-06 16:05 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Pollock CLA 2005-09-26 15:36:39 EDT 
3.1.1 RC2, GTK+ 2.6.8  
  
Take two MultiEditors, each with the same two editors.  In the first editor in 
the first MultiEditor, make a change.  The nested title of the editor 
indicates that it is dirty.  However, the dirty marker does not appear on the 
title for the MultiEditor.  It does not appear on the title of the second 
MultiEditor either. 
 
Now, switch to the second MultiEditor.  The MultiEditor title becomes dirty. 
 
Now, switch back to the first MultiEditor.  The MultiEditor title become 
dirty.
Comment 1 Douglas Pollock CLA 2005-09-26 15:41:19 EDT 
Correction: The tiled editor will only open if you have a different set of  
editors.  I've been just using a block of files: A, B, C, D and doing the  
following:  
    open A, B  
    open A, B, C  
    open A, B, C, D  
  
(org.eclipse.ui.examples.tilededitor)
Comment 2 Paul Webster CLA 2006-09-28 14:08:08 EDT 
Is this still a problem in 3.3?

PW
Comment 3 Denis Roy CLA 2007-06-22 09:33:05 EDT 
Changes requested on bug 193523
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:05:32 EDT 
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.