Bug 64911

Summary:	[navigation] AnnotationPainter and mark occurrences should use the visual annotation model
Product:	[Eclipse Project] JDT	Reporter:	Tom Hofmann <eclipse>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, daniel_megert, david.balazic, felix.saphir, fritzli_meier, markus.kell.r, mrj, remy.suen, thatnitind
Version:	3.0	Keywords:	investigate
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	107464

Description Tom Hofmann

2004-06-01 06:48:07 EDT

RC1

- browsing perspective (probably does not matter)
- smoke test scenario
- two editors open side by side
- open IMoney.java and Money.java
- enable Mark Occurrences, 'sticky' preference does *not* matter

- select a textual instance of IMoney in money

-> all IMoney instances in Money.java are highlighted
-> there is highlighting in IMoney.java as well, if the caret is placed on a
highlightable element

expected: there is only highlighting in the active editor

- Ensure that the caret in both editors is on a highlightable element, such that
 there is highlighting if the editor is active
- switch between the editors using Ctrl+F6

-> ok: there is only highlighting in the active editor

- switch between the editors using the mouse

-> not ok: there is highlighting in both editors.

Comment 1 Dani Megert

2007-03-20 13:51:50 EDT

*** Bug 107464 has been marked as a duplicate of this bug. ***

Comment 2 Dani Megert

2007-03-20 13:52:15 EDT

*** Bug 178289 has been marked as a duplicate of this bug. ***

Comment 3 Dani Megert

2007-03-20 13:56:20 EDT

The right way to solve this is to add the occurence annotation to the visual annotation model and change the AnnotationPainter to work on the visual annotation model.

This is quite a change and will probably add performance degradation as the visual annotation model delegates to the model's annotation model. Such a change needs closer investigation and testing.

Comment 4 Dani Megert

2008-02-29 03:18:20 EST

*** Bug 220835 has been marked as a duplicate of this bug. ***

Comment 5 Dani Megert

2009-07-30 02:19:34 EDT

*** Bug 284978 has been marked as a duplicate of this bug. ***

Comment 6 Dani Megert

2011-02-23 08:30:39 EST

*** Bug 337960 has been marked as a duplicate of this bug. ***

Comment 7 Eclipse Genie

2018-11-28 18:08:01 EST

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.

--
The automated Eclipse Genie.

Comment 8 Dani Megert

2019-06-12 09:16:10 EDT

*** Bug 548182 has been marked as a duplicate of this bug. ***

Comment 9 David Balažic

2019-06-12 09:27:55 EDT

(In reply to Dani Megert from comment #3)
> This is quite a change and will probably add performance degradation

I'm sure 15 years later the computers caught up with those computing demands.

Comment 10 Eclipse Genie

2021-06-02 15:24:29 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.

--
The automated Eclipse Genie.

Comment 11 Eclipse Genie

2023-05-31 17:13:49 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.

--
The automated Eclipse Genie.