gtg team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxxxxxxxx>]

On Sun, Mar 21, 2010 at 05:22:44PM -0000, Luca Invernizzi wrote:
> I thought it would be possible to disable the gtk.Calendar dates which
> do not satisfy our limitations (say, gray  unselectable dates).
> Unfortunately, that can't be easily done.

That would be the cleanest UI, although it would address only the case
where the user sets the due date via the calendars.  This can also be
done via dbus, plugins, or the context menu (by setting a due date in
the past, and then using the context menu to reschedule the task to
start tomorrow).

So, I think fixing it in the calendar widget would only paper over the
issue and incompletely.

I assume everyone agrees that due date before start date is not a valid
condition for a task to be in.  So currently this is a core bug.

If we fixed the validation to not permit it to begin with, then while
that makes the UI a little less intuitive, it at least converts a bug in
core to a (less severe imho) UI bug.

-- 
Start Date should not be allowed to be after the End Date
https://bugs.launchpad.net/bugs/532392
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: Confirmed

Bug description:
If a start date is set to be after a due date, the due date should be changed to reflect the start date. Currently, I have a task that starts in 11 days, but was due 15 days ago.. Yes.. I know, I am slacking with getting the task done.