Community
Participate
Working Groups
Build ID: I20080516-1333 Steps To Reproduce: 1. Create a DateTime widget 2. Add a double click mouse listener 3. Try to navigate from month to month using the arrows - doubleclick listener gets fired 4. Try to doubleclick on an actual date on the calendar - doubleclick listener gets fired. More information: Directly related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=229181 The issue is that the doubleclick handling is not useful to determine when a user doubleclicks on an actual date, instead of just doubleclicks anywhere on the control. Need some way to differentiate this event, or another place to add the mouse listener so that we can get the *useful* doubleclick events. Can this be fixed for 3.4 Release? (It's useful for us to know ahead of time so we can decide whether or not we can use this control for what we want.)
Realistically, this is an issue for all the mouse events - there's no way to determine what subpart of the control the event was for.
This can't be fixed in time for 3.4. Code is almost frozen now, and only critical bug fixes are going in. By any chance, can you use the Selection or DefaultSelection events instead? Selection is fired whenever a new date is selected with either the mouse or keyboard. Currently, DefaultSelection is only fired when the user types Enter, however it might make sense (in future releases) to also fire DefaultSelection when the user double-clicks on a date. You would not be able to distinguish between double-click and typing Enter, but I think that would be ok, because it is always desirable from an accessibility point of view to have a keyboard mechanism to fire an event.
I can't seem to get the default selection event to be fired using the enter button. Using same build as Chris mentioned above.
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.
