Thanks for the info, Monty. I'll play with it some tonight. But it happens that way on both my home and work WinXP PCs. Work PC is brand new first time ever DQSD install with very minimal tweaking.
Only thing in common... both are DELL Laptops. Can't see how that matters though. JB > This is a multi-part message in MIME format. > > > Clock QuestionHmmm thats freaky... I havent seen that before... I rebooted and watched to make sure I wasn't getting the same behavior... It seemed to switch to the clock automatically... Could it not be finishing prior processing (like the load history function for example) before initiating the timer? This is a stab in the dark, but you could try clearing the history.. Maybe one of the searches is having trouble loading? The only thing I have different in my localprefs.js is to update the clock every minute (if the clock isnt showing the seconds why update the display every second?).. and I dont have as many definitions in localprefs as you do... > > /* clock display delay in milliseconds > * every 1000=1 second ex: 5000=5 seconds > * default = 5000 > */ > clockdelay=2000; > > /* clock update rate in milliseconds > * every 1000=1 second > * default = 1000 > */ > clockupdate=60000; > > > /* Number of searches to remember. Lower this if you notice poor performance > * after a search. (The entire history is written to disk after each search.) > */ > historylength=100; > > > > None of this probably helps, but I thought I would post my ramblings anyway.. :-) > > Monty > John W. Bairen, Jr. www.bairen.net ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
