Bug 173581 - 'Go to Today' shortcut has been removed
Summary: 'Go to Today' shortcut has been removed
Status: RESOLVED INTENTIONAL
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-26 12:24 UTC by Adam Spiers
Modified: 2012-07-06 20:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Spiers 2008-10-26 12:24:24 UTC
Version:           4.1.0 (using KDE 4.1.2)
OS:                Linux
Installed from:    Fedora RPMs

Somewhere in between version 3.5 and 4.1.0, the 'Go to today' keyboard shortcut was removed from KOrganizer.  For obvious reasons this is a very important keyboard shortcut, so it's a noticeable regression to have to use the mouse to click the Today icon every time you want to return to the current day/week/month etc.  Please add it back in ASAP, thanks!
Comment 1 Allen Winter 2008-10-26 15:11:21 UTC
Adam,

Isn't there a "To Today" shortcut available to you in Configure->Shortcuts?

I don't remember having a default shortcut set for this action before.

Perhaps someone renamed the action from "Go to Today" to "To Today".
Comment 2 Adam Spiers 2008-10-27 10:04:42 UTC
Ahah!  You are right, that is why I didn't find it :-(  IMHO "To Today" is much less obvious, and it should be renamed back.  Also "Backward" and "Forward" used to be something like "Go Backward" and "Go Forward" which meant that all three actions were grouped together in the shortcut configuration window.  So I would suggest reverting all 3 (and in fact any other renames which didn't have a strong reason behind them, since they could needlessly confuse users after an upgrade).  Thanks a lot for the quick response! 
Comment 3 Allen Winter 2012-07-06 20:51:59 UTC
by now I'm not sure I want to rename these actions.

getting to 4 years since this bug was reported so maybe we shouldn't change it.
i could be persuaded otherwise, but in the meantime, I'm resolving this.