Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320953 - No indication of invalid hit count
Summary: No indication of invalid hit count
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 15:07 EDT by Darin Wright CLA
Modified: 2020-03-29 11:35 EDT (History)
2 users (show)

See Also:

Attachments
patch (2.16 KB, patch)
2010-07-26 15:07 EDT, Darin Wright CLA 		no flags Details | Diff
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 Darin Wright CLA 2010-07-26 15:07:31 EDT 
Created attachment 175263 [details]
patch

When editing a breakpoint's hit count in the breakpoint detail pane there is no indication when an invalid value is entered (letters, negative, etc.). It might be possible to use an error control decoration for this.
Comment 1 Darin Wright CLA 2010-07-27 11:30:14 EDT 
Apparently this style field specific error annotsions was not accepted for use in Wizards/Dialogs - since there was no way to automatically adopt the style in dialogs that already use message panes.
Comment 2 Dani Megert CLA 2010-07-28 01:50:01 EDT 
Not sure how often people run into that. For now the simplest thing might be to show an error (=> appears in red) in the status line.
Comment 3 Eclipse Genie CLA 2020-03-29 11:35:22 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.