So... I was looking through the API, and trying to figure stuff out... like what is in Metrognome that's not in AceEvent.
As I've mentioned, I'm not so grate and dis reedin stuf; would someone please help me understand what the difference between the two is? Specifically, why use Metrognome over AceEvent?
ckk put in repeating events, but I'm still not convinced it's the best way to go...
I personally am sticking to Metro because I can get much more specific profiling data in tekSupport from it. With metro I can factor in the timer's rate and get a "per second" resouce use... with AceEvent I can only get per-event numbers...
The only other thing I've seen is it's easy to change the rate on a metro timer... but I don't think it's horribly challenging to do the same in AceEvent.
I've been doing a lot of optimizations to AceEvent-2.0 regarding scheduling recently, and it's actually faster than Metrognome-2.0 now. The downside is that it can't be profiled as easily because of said optimizations.
I make no claims that Metro is faster than any specific library, if I did I'd give some proof with it *hint ckk*.
That being said, I do tout that metro is slim and fairly well optimized. No, I didn't spend hours of time to milk out every ms of exec time I could, but in the end it's gonna perform better than most author's use of onupdates, and that was the whole intent.... to put an end to some nasty code by providing a simple, slim alternative. I still stand by that.