Bug 182905 - [misc] IDocument Position vs undo-redo for text
Summary: [misc] IDocument Position vs undo-redo for text
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 182907 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-04-18 05:44 EDT by Peter Ossipov CLA
Modified: 2019-09-06 16:18 EDT (History)
1 user (show)

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 Peter Ossipov CLA 2007-04-18 05:44:19 EDT 
When working with IDocument interface you can use such a useful thing as Position. That is fine. I like it. 
Then there is a situation when I add the position and then edit the text and finally undo the text changes. In that case the position is being updated as normal, i.e. as if I just edited the text. So, that results in the position been somewhere but not where it was originally. So, could a proper undo-redo for positions been added and IPositionUpdaters are only consulted when a "proper" change to the text been made? 
Otherwise, the situation does not make much sense to me. And I have to listen to stack events and on undo-redo events restore the positions myself which I do not really enjoy.
Comment 1 Peter Ossipov CLA 2007-04-18 05:49:58 EDT 
*** Bug 182907 has been marked as a duplicate of this bug. ***
Comment 2 Dani Megert CLA 2007-04-18 17:53:04 EDT 
.
Comment 3 Dani Megert CLA 2007-06-22 09:59:33 EDT 
Get rid of deprecated state.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:18:11 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.