Bug 363335 - [breakpoints] Unable to scroll breakpoint conditions in view
Summary: [breakpoints] Unable to scroll breakpoint conditions in view
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 10:41 EST by DJ Houghton CLA
Modified: 2023-01-19 13:29 EST (History)
2 users (show)

See Also:

Attachments
screen shot (72.97 KB, image/png)
2011-11-09 10:41 EST, DJ Houghton CLA 		no flags Details
View All 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 DJ Houghton CLA 2011-11-09 10:41:10 EST 
Created attachment 206705 [details]
screen shot

When you have a conditional breakpoint you can edit the conditions within the Breakpoints view itself. Unfortunately there are no scrollbars in the text widget so you can make changes but you can't see what they are.

Screen shot attached.
Comment 1 Remy Suen CLA 2011-11-09 16:23:40 EST 
I have scrollbars on Windows 7 but it's not perfect. Wonder if it's the same cause as bug 362615 for the Mac.
Comment 2 Eclipse Genie CLA 2020-09-04 14:33:13 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 3 Eclipse Genie CLA 2023-01-19 13:29:26 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.