Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 509520

Summary:	Breakpoints view sorted by Creation Time/Name: adding breakpoints removes previous from view
Product:	[Eclipse Project] Platform	Reporter:	Markus Keller <markus.kell.r>
Component:	Debug	Assignee:	Sarika Sinha <sarika.sinha>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert
Version:	4.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug
Bug Depends on:	498426
Bug Blocks:

Description Markus Keller

2016-12-20 06:44:48 EST

I20161219-0145

Breakpoints view sorted by Creation Time has a problem when there are more breakpoints than are visible in the tree (i.e. when the tree has a scroll bar).

When you add more breakpoints in that case, only the breakpoint on the top gets replaced by the new breakpoints, but the second-to-last breakpoint gets hidden in the view. If you start scrolling around, the missing breakpoints reappear.

I guess the problem is with the virtual tree. In the "Sort By > Name" case, the list needs to be sorted after inserting a new item, so you get a refresh for free. When adding an item on top, that refresh doesn't seem to happen, so the older items don't get moved down.

Comment 1 Sarika Sinha

2017-01-06 01:53:56 EST

Observed the same problem will with Sort by "Name"

Add a breakpoint, which might land up some where towards the last of the view area and there are more breakpoints not visible in the tree. Adding a breakpoint just replaces the breakpoint position in the sorted place, rather than shifting it. Scrolling up and down to the next page brings it back. (Or closing and opening the view again).

Comment 2 Sarika Sinha

2017-01-06 04:38:10 EST

Discussed it with SWT folks, looks like a TreeViewer issue.
Even after calling refresh, it doesn't update all the time.
Looks like it marks the area for refresh, but does not refresh at the same time always.

Comment 3 Sarika Sinha

2017-01-19 23:55:51 EST

moving it out as of now as we don't have much idea about the possible solution.

Comment 4 Eclipse Genie

2020-04-12 19:18:54 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.