Bug 77864

Summary:	Different month view behaviour
Product:	[Applications] korganizer	Reporter:	George Staikos <staikos>
Component:	general	Assignee:	Cornelius Schumacher <schumacher>
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description George Staikos 2004-03-17 20:20:41 UTC

Presently the month view doesn't exactly map up to the mini calendar widget.  
If the user clicks on a date in the mini-calendar, the month view shifts to put 
that date on the top line.  I think, at least for me, the user expects to see 
the month view match what is visible in the mini-calendar widget.  I do see the 
value of the current system, but I think it would be ideal for this to be 
configurable, or to have a second style of month view that mirrors the 
mini-calendar.

Comment 1 Andy Payne 2004-05-05 20:28:08 UTC

This relates to my comments on BR56546, too.

The orange "Go Backward" and "Go Forward" buttons should, in Month View, navigate you backwards and forwards by 1 Month.  This is, afterall, the unit of time the user is obviously interested in.

And as stated in this BR/wishlist, the main view should reflect the mini-calendar widget, else it is very confusing.

This is not helped by the confusing way day-numbers have their background colour selected. It should be that days within the selected month (as selected in the mini-widget) have a white background to their number, and days from preceeding or proceeding months should have grey backgrounds. As it is now, 'grey' is used for the first day to be shown, and it alternates to white at a month boundary. This means that clicking 'Go forward' can change the background to a day's number, for no obvious reason.

I hope that makes sense.  I know it could be argued that this is a separate bug, but it relates very closely to this one and is part of the same issue.

Comment 2 Reinhold Kainhofer 2004-10-03 18:22:05 UTC


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