Re: [DQSD-Devel] Clock Question

[Monty Scroggins]

Title: Clock Question

Hmmm 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