Absolutely right! I haven't been able to get this to happen at all, and
I've tried doing things different than my normal way. It might be a
long sequence of things that makes it happen, though, and therefore hard
to reproduce. But obviously, once we can do it "on demand", we can
squash it like the insect that it is...
--Byron
Engstrom wrote:
>
> Todd,
>
> how long were the runs? I don't know how Byron's code works, but
> the length of the runs could play a part. If they were all the minimum
> time, then it might not trigger the condition which causes some runs
> not to be deleted.
>
> By the way, thanks for taking the time to try and re-create the problem.
> I have a feeling the more of us trying to recreate it the more successful
> we'll be. Intermittent problems are a pain to track down.
>
> John "No, not that one" Engstrom
>
> ----------
> From: Todd Green[SMTP:tag@cs.utah.edu]
> Sent: Friday, August 27, 1999 9:18 PM
> To: geez@autox.team.net
> Subject: Re: Deletion bug on the Palm...
>
> >There might be a little more to it than "Any additional deletions
> >appeared to work, but upon exiting and re-entering the download
> >app, they re-appeared." I've used Geez and the Palm to record
>
> Crap. I have to agree. I just did a bunch of dummy runs (manual start
> with the cube sitting on my desk, wait the min five secs, and manually
> stop the run)
>
> I create 2-3 dummy runs then went to download and deleted all of them
> and reran download. Worked like a charm. Recorded more dummy runs,
> deleted them...did it a 3rd time...still worked.
>
> I could not reproduce the behavior of yesterday at all.
>
> Todd
|