On Oct 30, 2004, at 11:40 AM, Paul McNett wrote:
> Eventually, I'm going to hide all the wx methods in the docs, so even
> though they are there their use will be discouraged when there are
> higher-level Dabo ways to accomplish the task. I think we must be
> consistent with ourselves, and not worry about duplicating names with
> the underlying toolkit we happen to be using.
Are you going to also hide them in the editors? I had originally added
enable(), and when I pulled up the 'command window' and typed in some
code, I noticed the duplication in the intellisense.
> Actually, I liked that the timer would automatically start with a
> positive Interval and stop with a 0 interval - I like VFP-like timers
> because they are simple and I don't need to remember anything but
> setting Interval and writing the code to run when Interval is reached
> - but that's a different argument I don't have time to participate in
> at the moment unfortunately! :)
Explicit is better than Implicit. ;-)
I'd prefer to be able to configure the timer ahead of time, and start
and stop it as needed. When I set the interval, I don't expect it to
start firing away. VFP timers behave more like the way I've changed
dTimer: you can set the interval and nothing happens if the timer is
disabled. You can stop the timer and it still remembers its original
interval. I remember the discussion during the VFP 3 beta about the
practice of stopping the timer by setting the interval to zero, and the
explanation is that was more of a side-effect than an intended
practice; otherwise, a zero interval would be the equivalent of a tight
infinite loop.
___/
/
__/
/
____/
Ed Leafe
http://leafe.com/
http://dabodev.com/
©2004 Ed Leafe |
