Go to Page... |
Updated: | 11-13-12 10:54 AM |
Created: | 08-22-12 04:23 PM |
Downloads: | 510 |
Favorites: | 2 |
MD5: |
File Name |
Version |
Size |
Author |
Date |
1.10.29.1 |
306kB |
Wykkyd |
10-29-12 04:27 PM |
|
1.3 |
21kB |
Wykkyd |
08-22-12 10:01 PM |
|
1.1 |
21kB |
Wykkyd |
08-22-12 09:12 PM |
|
1.0 |
13kB |
Wykkyd |
08-22-12 04:23 PM |
Comment Options |
08-22-12, 08:52 PM | |
FYI known issue already with the event I'm tracking. Runs too often & bogs down in a raid. I will have a fix shortly. Sorry folks
|
|
|
Wykkyd |
View Public Profile |
Send a private message to Wykkyd |
Send email to Wykkyd |
Find More Posts by Wykkyd |
Add Wykkyd to Your Buddy List |
Wykkyd |
View Public Profile |
Send a private message to Wykkyd |
Send email to Wykkyd |
Find More Posts by Wykkyd |
Add Wykkyd to Your Buddy List |
08-23-12, 07:42 AM | |
Thanks to early adopters!
Thanks for the quick support, guys, and the patience. This was my first addon and I was learning event hooks as I wrote it. Special thanks to Wildtide for building such a smooth UI pack, it made things easier.
Now, make sure to grab the latest version folks. CPU utilization of Trinket Spy went from an average 5% to ... less than .1%. Lesson learned (for other devs): Event.System.Update.Begin seems to fire every micronanoholycrapslowdown second. I added a Return break at the top of my update function to force it to do nothing if .75 seconds hadn't elapsed yet. This saved the day. I could probably reduce this a tad and get the Cooldown ticker a tiny bit smoother but I don't really know that it's worth bothering with. |
|
|
Wykkyd |
View Public Profile |
Send a private message to Wykkyd |
Send email to Wykkyd |
Find More Posts by Wykkyd |
Add Wykkyd to Your Buddy List |