That's definitely a new bug I hadn't noticed before.
If you could, please look into it as part of fixing Bug #4.
When Kaboodle starts, it should presume all devices are
inactive until it determines conclusively that they are
active. It should not corrupt the "last active time" data,
as you point out.thanks, Scott On Fri, 21 Mar 2003, Kaboodle Team wrote: > Bug #4 is fixed. > All related source code will be checked in today. > > While working on it I've found yet another malfunction: > > When I start the Kaboodle that already knows this PC, > it first draw all network devices as inactive - I think > it is right. > Then after first network scan (as I think) it draw all > network devices as active in spite of the fact that one > of network devices is turned off (in my testing). > And only after 3-rd scan Kaboodle draws inactive PC as > inactive. > Such a behaviour hardly could be considered as normal. > But this malfunction is not pointed in your bug list. > What do you think about it? > > As I already wrote when Kaboodle starts it for small time shows > inactive PC as active. But what is worse as it considers PC as active > it saves current time as last active time. > So I could turned some PC off 2 weeks ago but Kaboodle will report > it looks this PC active only 1 minute before. I think it fully > brokes all time logging support. ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
