On 24 Sep 2002 at 19:48, Fringe Ryder wrote: Hi Tony,
> First off, my first assumption was that PluckerDesktop would maintain your > "Base Time", such that the Pluck of a channel could go off at 5am every day > regardless of what else has happened. This is clearly wrong, because I set > them to 5am and wound up with all sorts of odd minutes in them. Yes, this is a misfeature at the moment. The dropdown is a placeholder for the time being. There should be a custom control for a masked edit ctrl for entering in a time, or else a custom control for hours and minutes made of 2 spin controls. It would probably be better time management to start with a proper control and work from there, instead of putting more effort into polishing up the current dropdown control aproach. The current code was built to work with a control that has minutes in it. There is a TODO.txt that has a list of these types of things that would be good additions to have. Interested in writing it? You can look around at some of the other custom control classes in the plucker-desktop source to get the general feel, such as any of the *_listctrl controls. It would then just need a "unknown" placeholder in the XML resource file, and the custom class gets inserted into its placeholder at runtime. > I just did a Pluck, from about 18:30 to about 18:53, 24 Sept 02. > > Channel 1, BBC News... is scheduled to go hourly. It actually finished > writing that pdb at 18:37, but isn't rescheduled until 19:47, which is an > odd time considering the Pluck wasn't done with all the channels by then > but was long done with the BBC. In other words, a bit over the scheduled hour. If the update_base in the config file is 18:37, and is scheduled to go every hour, after it is updated, the new update_base is 18:47. AFAIK, this is how the scheduling works in RSS and scheduling and elsewhere. > Channel 2 is BusinessWeek. That file datestamp is 18:38. That's scheduled > to update every six hours, but it came in at 21:14. That's significantly > less than six hours, and it's not even close to an even multiple of six > over the 5am it was initially set for. I am unfortunately unable to reproduce any problem with advancing the update_base. I make a channel with an update base of 10:00, and set it to update hourly. I start my computer at 13:34, as soon as the program notices it overdue, it updates it, and advances the update_base in hour increments until it has caught up to where it should be. So after an update, the update_base is 13:00 (giving a next due time of 14:00), as it should. There is a precision control on Preferences dialog > autoupdate tab that can set the granularity of how often it will check the current time against due times in the config file. Best wishes, Robert _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
