Bug 306943

Summary:

[breakpoints] Breakpoints view: Line breakpoint details pane too small initially

Product:

[Eclipse Project] JDT

Reporter:

Markus Keller <markus.kell.r>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

CC:

daniel_megert, deepakazad, Michael_Rennie, robin, sarika.sinha

Version:

3.6

Target Milestone:

---

Hardware:

OS:

All

Whiteboard:

stalebug

Attachments:

Description	Flags
Screenshot	none

Description Markus Keller

2010-03-24 10:33:08 EDT

Created attachment 162863 [details]
Screenshot

I20100323-0800

Start a new workspace, don't resize the window. Paste a class, add a line breakpoint, switch to the Debug perspective, and select the breakpoint.

=> Only 1 pixel of the 'Conditional' text area is visible, and depending on how the window is redrawn, it's not even visible completely. 

I think the text area should have a minimal height. Problem is: What height? On Windows, 1 text line would suffice since Windows does not show the horizontal scrollbar if there's not enough space. But e.g. on GTK, the scrollbar is always shown, so I guess you need to use computeTrim(..) to add the height of the scrollbar as well. Bug 27096 would make this a bit easier.

Additionally, you could enlarge the details pane when the user checks 'Conditional' and the pane is smaller than the minimal size.


Example class to paste:

public class C {
	public static void main(String[] args) {
		int i= 2;
		System.out.println(i);
	}
}

Comment 1 Dani Megert

2012-05-08 09:10:52 EDT

FYI: Bug 27096 got fixed for 3.8.

Comment 2 Eclipse Genie

2019-12-08 12:22:46 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 3 Sarika Sinha

2019-12-08 23:32:11 EST

Problem can be seen with 4.14 also.

Comment 4 Eclipse Genie

2021-11-28 11:13:03 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 5 Eclipse Genie

2023-11-19 08:44:17 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.