Bug 28742 - Adding break point updates hierarchy view
Summary: Adding break point updates hierarchy view
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1   Edit
Hardware: PC Linux-Motif
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2002-12-20 10:29 EST by Andrew Irvine CLA
Modified: 2005-03-08 03:57 EST (History)
3 users (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 Andrew Irvine CLA 2002-12-20 10:29:04 EST 
Eclipse 20021218

Display the hierarchy view for an open file.  Now add a breakpoint to a method 
of that file.  Note the flash in the hierarchy view.
Comment 1 Darin Wright CLA 2003-01-03 11:33:27 EST 
Moving to JDT-UI. The breakpoint action has no knowledge of the hierarchy view.
Comment 2 Dirk Baeumer CLA 2003-01-07 09:56:02 EST 
Can't reproduce under Windows. Adam, do you see it under Linux. If so, please 
move PR to Martin, otherwise close.
Comment 3 Adam Kiezun CLA 2003-01-07 10:07:38 EST 
i do see it - only on Motif
both outline and hierarchy views flash when i add/remove a breakpoint
Comment 4 Martin Aeschlimann CLA 2003-01-07 11:32:06 EST 
All views showing elements from working copies are concerned:
The errortick manager listens to annotation-model changes in the editor.
Every add/remove of a annotation leads to a image update as we currently have 
no information of the annotion which changed.
Moving to jdt-text: More information in the delta would solve the problem. 
(Unfortunatly this is quite tricky to change as this is all API)
Comment 5 Tod Creasey CLA 2005-03-07 11:57:16 EST 
Adding my name to the cc list as we are now tracking performance issues more
closely. Please remove the performance keyword if this is not a performance bug.
Comment 6 Martin Aeschlimann CLA 2005-03-08 03:57:31 EST 
bug is outdated. was fixed at least for 3.0 (probably even for 2.1.x)