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

Bug 189769

Summary: [Dialogs] TwoPaneElementSelector doesn't display validation errors nicely
Product: [Eclipse Project] Platform Reporter: Grant Taylor <gdtaylor>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 Keywords: helpwanted
Version: 3.2.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Grant Taylor CLA 2007-05-29 15:58:09 EDT 
In our product, we have subclassed the TwoPaneElementSelector dialog and provided our own validator.  However, when our error message is displayed I see the following two behaviours:
1) The text is clipped.  Perhaps space for two lines of text could be alloted since our errors always result in the user having to resize the dialog.
2) The error icon isn't shown if there isn't enough room.  Since our error message always run out of room, the icon isn't shown either (as per CLabel class).  This is doubly bad because the user just sees some garbled text and may not know why it's there at all.  The presence of the error icon is probably the most important visual indicator that the current selection is invalid.  I think the icon should always be shown.

This defect also occurs in version 3.0.2 of Eclipse (we have another version of our product being released on this older version).
Comment 1 Susan McCourt CLA 2007-06-27 16:46:11 EDT 
as you noted, this is the behavior of CLabel.  To fix this would require reimplementing the MessageLine.  Ideally I'd like to see a common message area used among all the dialogs (for example, see bug #11233, bug #148085)
Comment 2 Susan McCourt CLA 2009-07-09 17:19:43 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Eclipse Genie CLA 2019-09-04 16:45:43 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.