Bug 232169 - 'Today' button not greyed in Month view
Summary: 'Today' button not greyed in Month view
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: LO normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-26 00:20 UTC by Sabine Faure
Modified: 2017-01-07 22:02 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 Sabine Faure 2010-03-26 00:20:37 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch KOrg
- Click on 'Month View' button

The 'Today' button from the main toolbar is available however nothing happens when clicking on it.

I am wondering if it would not be better to make it unavailable (greyed) if it indeed does nothing at all.

Trunk, Svn Rev 1107335
Comment 1 Sergio Martins 2010-03-26 02:15:09 UTC
"Today" makes today visible, it probably was already visible when you clicked it.

If you click it when in another month, it will work.

But i guess you're still right, when today is visible, "Today" button should be greyed.
Comment 2 Sabine Faure 2010-03-26 21:27:29 UTC
Sergio, thx a lot for the clarification. ;o)

I retested this today and yes when the Month view is displaying another month than the current one, clicking on the 'Today' button goes back to the current month.

But yes, it will be more intuitive to have the button greyed when looking at the current month.

Trunk, Svn Rev 1107667
Comment 3 Denis Kurz 2016-09-24 18:52:26 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:02:09 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.