After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617458 - Time and Date key Bindings
Time and Date key Bindings
Status: RESOLVED DUPLICATE of bug 611576
Product: orca
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal enhancement
: ---
Assigned To: Orca Maintainers
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-02 17:37 UTC by Scott Berry
Modified: 2010-05-02 17:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Scott Berry 2010-05-02 17:37:07 UTC
There has been some talk on the Orca list about adding date and time keys to Orca by default.  However, there are some concerns as 

to how the keystrokes should be handled.  Here are the ideas:

1.  F12 can be pressed for time and a double F12 for date.  Also noting that F12 is used by Jaws so this may be a litigation 

concern.  However, it has been mentioned that keyboard layouts could be packaged like translations and you can then add the 

keyboard layout of your choice to Orca.

2.  Control Plus T could be used for Time and Control D for date.  It would be cool if the date and time was also sent to the 

clipboard and if you need the date or time on a project anywhere else inside the Gnome environment you have it on the clipboard 

till you overwrite it.  Then you just go grab it again.

The consensus states however, that Control Plus T and Control Plus D would be fine so this is probably what the RFE should use.
Comment 1 Joanmarie Diggs (IRC: joanie) 2010-05-02 17:44:23 UTC
Scott. Thanks so much for doing this. I'm afraid it didn't occur to me that you might not be familiar with which RFE's had already been filed. I'll email you the threads to start with. However, we already have an open RFE for this one. I'm really, really sorry!

*** This bug has been marked as a duplicate of bug 611576 ***