Bug 177764 - [DateTime] Calendar navigation enhancements
Summary: [DateTime] Calendar navigation enhancements
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-16 10:55 EDT by Frank Rydzewski CLA
Modified: 2021-11-12 11:47 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Rydzewski CLA 2007-03-16 10:55:43 EDT
When navigating the DateTime component (in SWT.CALENDAR mode), it would help if the selection behavior was enhanced/changed.

I intend to use the calendar in a popup component, where the popup should close when the user selects a date.

Specific requests:
 - when changing month or year via the controls at the top of the calendar, do not automatically assume the selection should change to the same "day of month" as was previously selected.  Instead, just set focus to that date and allow the user to press enter or mouse click that date to indicate selection.
- when navigating by keyboard, allow the user to use some sort of key combination (ctrl+arrows comes to mind) to move focus in the calendar *without* affecting selection.  This includes navigating to the next or previous month. Pressing enter (and/or spacebar?) would then cause the focus date to be selected.

By causing selection to change during any navigation, it makes it difficult to discern whether the selection was intended by the user or just a side-effect of navigating to the actual selected date.

Another possibility for helping clarify the user's intentions would be to implement more events for this widget. (double-click, single-click, defaultSelection).  These would at least enable us to map a specific action to designate "select this date" and reduce the need to implement "noise-filtering" logic throughout our application.
Comment 1 Frank Rydzewski CLA 2007-03-16 11:32:34 EDT
(In reply to comment #0)
> Another possibility for helping clarify the user's intentions would be to
> implement more events for this widget. (double-click, single-click,
> defaultSelection).  These would at least enable us to map a specific action to
> designate "select this date" and reduce the need to implement "noise-filtering"
> logic throughout our application.
> 
bug 177776 requests additional events
Comment 2 Frank Rydzewski CLA 2007-03-16 11:35:14 EDT
(In reply to comment #0)
> - when navigating by keyboard, allow the user to use some sort of key
> combination (ctrl+arrows comes to mind) to move focus in the calendar *without*
> affecting selection.  

Strangely, you can single click and hold down the mouse button while dragging the cursor around the widget and cause the focus rectangle to move to other dates.  However, upon releasing the mouse button, the selection immediately changes to the date that has the focus rectangle.
Comment 3 Carolyn MacLeod CLA 2008-03-13 16:19:55 EDT
The Windows MonthCalendar control has a new style on Vista called MCS_NOSELCHANGEONNAV which is probably what we would want for this.
We might add this as a "hint" style some day (meaning only some platforms would support it), but not for 3.4.

Bug 165251 also talks about using an event to solve this problem, as well as the bug that you mentioned in comment 1.

I think that the behavior that you noticed in comment 2 is probably an artifact of MonthCalendar's support for selecting a range of dates.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:17:25 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.