Bug 156771 - [NoteTextLabel] WrapLabel position changes upon multiple invocations with same text.
Summary: [NoteTextLabel] WrapLabel position changes upon multiple invocations with sam...
Status: NEW
Alias: None
Product: GMF-Runtime
Classification: Modeling
Component: General (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal
Target Milestone: 2.1   Edit
Assignee: Cherie Revells CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-08 17:09 EDT by Syed Atif CLA
Modified: 2010-07-19 21:56 EDT (History)
1 user (show)

See Also:


Attachments
stack trace (41.49 KB, text/plain)
2006-09-08 17:16 EDT, Syed Atif CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Syed Atif CLA 2006-09-08 17:09:34 EDT
In the TextDirectEditManager, the TextCellEditorLocator#relocate gets called multiple times upon every key press.

The main issue is that every time it is called even when the text of the WrapLabel hasn't changed, wrap label changes its position and then back upon the next invocation of relocate. Since the Text cell editor is anchored to the wrap label and because the relocate gets called multiple times, this causes the Text cell editor to move very quickly upon every key press.
Comment 1 Syed Atif CLA 2006-09-08 17:16:12 EDT
Created attachment 49775 [details]
stack trace

this is a stack trace at relocate that shows what happens when a user does the following:

1. Create a note on the diagram.
2. Type in "This"

the format of the stack trace is as follows: first line shows the text in the WrapLabel, the next line shows the bounds of the WrapLabel figure and finally the proc. stack.

As you can see, relocate gets called multiple times. During these times, WrapLabel 'x' position changes even when the WrapLabel text is the same.
Comment 2 Anthony Hunter CLA 2007-06-19 11:44:22 EDT
Moving to the next release, GMF 2.1. 
Comment 3 Eclipse Webmaster CLA 2010-07-19 21:56:28 EDT
[GMF Restructure] Bug 319140 : product GMF and component
Runtime was the original product and component for this bug