Comment 1 for bug 474994

Peter,

 I knew we were in trouble when we left the career center on thursday with
an idea of what to do but nothing solid actually completed. I think we need
to tell Frank that we need two/three more weeks at the minimum to work out
the kinks in the program. I know that I haven't been engaged much recently
in the project, due to my college application and a family emergency. But I
am now in a better position to become more engaged in the project. What we
need to do next tuesday is fix atleast one of the problems. We shouldnt rush
to finish all of them, because that will likely lead to more problems rather
than solutions. So lets take our time with this project and really clean up
the code so that it is in pristine condition when we give it to Frank.
Hopefully avoiding an awkward situation like this tuesday.

Sincerely,
 Robin

On Wed, Nov 4, 2009 at 9:19 PM, Peter Hufford <email address hidden>wrote:

> Public bug reported:
>
> If either "Start Now" or "End Never" are unchecked "Start Date and Time
> does not change to unselectable the way it should. This is probably just
> due to sloppy programming on my part. I'm just reporting the bug so I
> remember to fix it.
>
> ** Affects: timelapse
> Importance: Medium
> Assignee: Peter Hufford (peterhufford)
> Status: Confirmed
>
> ** Changed in: timelapse
> Assignee: (unassigned) => Peter Hufford (peterhufford)
>
> ** Changed in: timelapse
> Importance: Undecided => Medium
>
> ** Changed in: timelapse
> Status: New => Confirmed
>
> --
> problem with unselectable for "Start Date and Time"
> https://bugs.launchpad.net/bugs/474994
> You received this bug notification because you are a member of TimeLapse
> Team, which is the registrant for TimeLapse.
>
> Status in TimeLapse - data recording for the XO laptop: Confirmed
>
> Bug description:
> If either "Start Now" or "End Never" are unchecked "Start Date and Time
> does not change to unselectable the way it should. This is probably just due
> to sloppy programming on my part. I'm just reporting the bug so I remember
> to fix it.
>