Bug 366369 - widgetDefaultSelected Event not fired cause of disabled default Button
Summary: widgetDefaultSelected Event not fired cause of disabled default Button
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.8   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-12-12 05:21 EST by Michael Seele CLA
Modified: 2020-08-23 02:17 EDT (History)
3 users (show)

See Also:


Attachments
Snippet (1.77 KB, text/x-java)
2011-12-12 05:21 EST, Michael Seele CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Seele CLA 2011-12-12 05:21:54 EST
Created attachment 208247 [details]
Snippet

Seems that the widgetDefaultSelected Event will not be fired when the Shell has a disabled default Button. When the button is not the default button, a event will be fired.
Under Windows, the event will be fired when the default button is disabled.

This has been tested with SWT S-3.8M4-201112091447.
Comment 1 Felipe Heidrich CLA 2011-12-19 12:20:47 EST
you are not getting widgetDefaultSelected in Text (and Combo) when the button is disabled.

if you add a SWT.Selection listener to the default button, does that get fired ?
Comment 2 Michael Seele CLA 2011-12-20 02:30:16 EST
(In reply to comment #1)
> you are not getting widgetDefaultSelected in Text (and Combo) when the button
> is disabled.

Yes. Please see the attached snippet, it shows the problem.

> if you add a SWT.Selection listener to the default button, does that get fired
> ?

No, it's not getting fired.
Comment 3 Xi Yan CLA 2018-08-16 16:54:51 EDT
I can reproduce the issue on SWT master as of today with GTK3.22.
Comment 4 Eclipse Genie CLA 2020-08-23 02:17:10 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.