Originally Posted by Rythal
The only reason I use debugprofilestop is as a time keeper for how often the quest window can update, without the checks it was updating several times per second and causing rather large overhead. The window can be updated for any number of reasons and there is a half dozen calls or more through out the code to do the update, so it was easier to use a function as percise as possible to ensure the most accurate timing of the redraws...
already some people don't like the small delay I do have in place, prefering the old way of instant window update as things happen.
|
Perhaps a setting, I know that's what ovale does (its the other addon I have that has a lot of overhead). Ovale has a throttle slider that delays the next update from 0 to 500 ms (unless an event causes ovale to need to update first).