Bug 382358 - [Dialogs] CCombo doesn't work properly with PopuDialog
Summary: [Dialogs] CCombo doesn't work properly with PopuDialog
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-06-12 08:59 EDT by Beat Schaller CLA
Modified: 2019-06-12 05:07 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Beat Schaller CLA 2012-06-12 08:59:48 EDT
Build Identifier: I20120315-1300

We have some CCombo in a PopupDialog. Normal behaviour is okay - open the dialog - select and save content of the dialog.

If someone opens the dialog and clicks beside the dialog, then the popup dialog doesn't close anymore. This behaviour differ to the standard behaviour of a popup with normal combo. If i click beside the dialog the popup disappears.

The reason for this:
In the PopupDialog in the method configureShell, in the listener for SWT.Deactivate is a check for shell childs! So it works no more.


Reproducible: Always

Steps to Reproduce:
1.create a PopupDialog
2.insert a CCombo
3.Open the PopupDialog
4.Click beside the PopupDialog
5.The PopupDialog is still visible, but should disappear
Comment 1 Niraj Modi CLA 2013-09-11 05:23:36 EDT
popupdialog is in JFace, that's why assigning it to UI team.
Comment 2 Dani Megert CLA 2013-09-11 08:10:09 EDT
(In reply to Beat Schaller from comment #0)
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.create a PopupDialog
> 2.insert a CCombo
> 3.Open the PopupDialog
> 4.Click beside the PopupDialog
> 5.The PopupDialog is still visible, but should disappear

Please attach a small snippet that demonstrates the problem.
Comment 3 Eclipse Genie CLA 2019-06-12 00:59:14 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 4 Dani Megert CLA 2019-06-12 05:07:28 EDT
No answer for more than 5 years. Closing.