In my ini-file, I had a timer_interval:500. This value is
read as the value '0' in the new dialogs (which only has
1 second interval for setting timer_interval and
timer_start_delay.
The new dialog should accept intervals of at least as
small values as 0.5 seconds - possibly also finer grade.
when saving the configuration the value '0' is written
instead of the original 500 (.5 seconds). It is not
possible having a value smaller than 1 second for either
of these fields.
This gives the following traceback when filtering should
start:
Traceback (most recent call last):
File "C:\PROGRA~1\_DEV\Python23\lib\site-
packages\win32com\server\policy.py", line 275, in
_Invoke_
return self._invoke_(dispid, lcid, wFlags, args)
File "C:\PROGRA~1\_DEV\Python23\lib\site-
packages\win32com\server\policy.py", line 280, in
_invoke_
return S_OK, -1, self._invokeex_(dispid, lcid, wFlags,
args, None, None)
File "C:\PROGRA~1\_DEV\Python23\lib\site-
packages\win32com\server\policy.py", line 601, in
_invokeex_
return DesignatedWrapPolicy._invokeex_( self, dispid,
lcid, wFlags, args, kwArgs, serviceProvider)
File "C:\PROGRA~1\_DEV\Python23\lib\site-
packages\win32com\server\policy.py", line 541, in
_invokeex_
return func(*args)
File "C:\Programfiler\_UTIL\spambayes_cvs\spambayes\O
utlook2000\addin.py", line 383, in OnItemAdd
self._StartTimer()
File "C:\Programfiler\_UTIL\spambayes_cvs\spambayes\O
utlook2000\addin.py", line 324, in _StartTimer
self._DoStartTimer(delay)
File "C:\Programfiler\_UTIL\spambayes_cvs\spambayes\O
utlook2000\addin.py", line 313, in _DoStartTimer
assert delay, "No delay means no timer!"
exceptions.AssertionError: No delay means no timer!
Logged In: YES
user_id=14198
Dialogs may be flakey for a little while. I agree we should
give finer grained control and 1 second. Please re-open if
this doesn't happen in a week or so.
Logged In: YES
user_id=583713
Fixed in cvs to allow half increments. Allow 4-24 hours for
anon-cvs to update.