Summary: | [DateTime] Calendar navigation enhancements | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Frank Rydzewski <frydzewski> |
Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | bradleyjames |
Version: | 3.3 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Frank Rydzewski
2007-03-16 10:55:43 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 (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. 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. 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. |