As for the trinkets, it is a side effect of equipping one. Unfortunately the workaround is big, complicated and ugly. I plan on putting it into the rewrite (which will have a different name), but not in this one. Sorry about that.
No problem. I realise that anything with multiple cooldowns is going to be 'fun' to code elegantly.
Basically for those that want the details, trinkets have 2 cooldowns.. One when you equip, which is usually shared with other trinkets, and one when you use, which is usually shared with other trinkets of the same type (eg, one that gives you AP on use will share with another that does the same, but not one that gives you crit on use)..
I make it 3 cooldowns =)
30s cooldown when first equiped - not shared
Cooldown shared by trinkets of the same 'type' to prevent two running at once. Runs for the duration of the buff
Cooldown of the actual trinket used itself - not shared
Cood catch.. I had been wondering why my trinkets that were on cooldown when i didnt use them had different cooldowns each time i used a different trinket.. now it makes sense, it's up for the duration of the buff you get from using on of the other ones..
To unhide the drag boxes, you must unlock each group.. Right click on the CDT icon, go to group settings, select a group, and uncheck the locked option.
I had been trying to track down why pulse on hit wasn't working all the time, and didnt even think it might be related to ranks.. thx, I am going to check that out now...
Ah, there it was :)
Seems the pulse bug it's not related to the rank after all, it happens when I SPAM a button, possibly hitting multiply buttons at once.
Hm. So to clarify, the only time that pulse _is_ working for you is if you spam?
To be fair, it only bugs like once a day or so when you're in a pinch :)
To clarify, it bugs when I button mass.
Though it only bugs for the spell that I cast and a reload fixes it.
Yes, I'm able to reproduce with only CooldownTimers2 active.
HowTo: You really have to SPAM your buttons, and not just 1 button, multiply button. I did it with spamming QWERT all at once. Also the spell was already on cooldown, but not sure if this is important for reproducing.
Q = Counterspell
W = Strafe left
E = Move forward
R = Strafe right
T = Blink
To be fair, it only bugs like once a day or so when you're in a pinch :)
To clarify, it bugs when I button mass.
Though it only bugs for the spell that I cast and a reload fixes it.
Yes, I'm able to reproduce with only CooldownTimers2 active.
HowTo: You really have to SPAM your buttons, and not just 1 button, multiply button. I did it with spamming QWERT all at once. Also the spell was already on cooldown, but not sure if this is important for reproducing.
Q = Counterspell
W = Strafe left
E = Move forward
R = Strafe right
T = Blink
Hope it helps.
That sounds more like an issue with the blizzard code. Addons don't just bug because of spamming, especially not with a specific case of multiple button spamming, so that has to be something in the C code, not the lua code (most likely in the keyboard stuff).... Sorry to say, because I hate going there myself, but since you can reproduce it easily, and I can't at all (not even using your method), could you report this on the blizzard bug forum?
I only had a quick look though the thread,
so I don't know if it isn't asked already:
I'm having my spell cooldowns growing upwards (Global Setting) and
my ItemCooldown set growing downwards (overwriting global setting) but
it seems CDT2 seems to ignore my ItemCoolDown setting.
So I have to manually set it to grow downwards each time
I log on or reload the interface.
The fubar plugin shows that its set as growing downwards, which isn't the case.
So I guess the setting is saved but not recalled correctly.
And are the fixes provieded here already included into the official release or
should I download the modified release?
Found this in the CooldownTimers 2.0 thread and it's happening to be too and he said it just like I would so I'll just c/p it. :p
Found this in the CooldownTimers 2.0 thread and it's happening to be too and he said it just like I would so I'll just c/p it. :p
Where was this copied/pasted from? Any problems with the official release that result in a modified release need to be reported here so I can fix them, thus ending the modified release.. You have just reported it, and I will look into it, but I would like to get in touch with this person to let him know the proper method for reporting issues.
Not really sure what I should say to them, since the spells are cast as they should thus the key press is registered.
But I can point out that there is an issue with this addon.
Typing my thoughts out as they come to me, so just ignore contradictory statements =)
The more I think about this, the more I don't wonder if maybe there is just something weird about either your machine, or your install of wow, or some combination of addons, and not what I had said previously. Perhaps another addon you are using is tainting the codepath somewhere. But then again you said that you are able to reproduce it with just cdt running... unless maybe it's something that cdt depends on that is doing it.. It's very strange that it would only happen when you spam several buttons at once, and even then only when you are really trying to reproduce it..
However, I do see some other glitches when spamming buttons, such as when my hearthstone is on cd, and I spam the 1 key (which right now is the reins for the new goats), I can see the hearthstone bar refresh every few keypresses. In other words, the bar will basically act like it is going to start over, and then drops back to what it was at before, all in less than a quarter of a second.. Literally it is a flash that is just over the threshold of how fast it would have to disappear for the human eye to not even register it. Maybe the problem isnt in the cdt code, but in the candy bar code.. I'm not sure when I will have time to check it out, but I will take a look. For now just hold off on reporting it to blizzard.
Where was this copied/pasted from? Any problems with the official release that result in a modified release need to be reported here so I can fix them, thus ending the modified release.. You have just reported it, and I will look into it, but I would like to get in touch with this person to let him know the proper method for reporting issues.
Looks like you found it and when I started looking at the dates of the replies there it also seems to be very old, no idea why it was so high in the General Addons list. Never the less it still isn't fixed so at least I did something else then bumping an old thread. :p
Hope it helps a little, also I'll edit in a link to the bug report on the forums when I get that done :)
Unfortunately that doesn't help me reproduce it on my rogue, however I am able to unreliably reproduce it on my rogue now with ghostly strike, as I was farming motes a couple nights ago and noticed that the ghostly strike bar stopped pulsing but it started again after i reloaded. I'm trying to track it down now.
In trying to config CooldownTimers2 using the Rock config screen, I am getting this message in Bug Sack:
[2007/10/12 15:14:28-968-x2]: CooldownTimers2\Options.lua:1108: attempt to index field '?' (a nil value)
Anyone have any ideas on why?
Thanks in advance,
Red
Don't use rock to configure CDT, the layout of the GUI was designed for waterfall, so the only supported (working) config method is thru the GUI that you get when you left click the minimap or fubar icon, or type /cooldowntimers gui
Thanks for the quick response, Speeddymon, and I love your addon. For some reason, I am not getting the Waterfall menu to work correctly. When I left click the fubar option, nothing happens, and when I do a /cooldowntimers gui command, it tells me it is invalid. I can right click the FuBar icon and get the drop down menu, but what I am looking to do is put all my item cooldowns under the CDT menu. Is there a way I can do this by /slash command?
Thanks for the quick response, Speeddymon, and I love your addon. For some reason, I am not getting the Waterfall menu to work correctly. When I left click the fubar option, nothing happens, and when I do a /cooldowntimers gui command, it tells me it is invalid. I can right click the FuBar icon and get the drop down menu, but what I am looking to do is put all my item cooldowns under the CDT menu. Is there a way I can do this by /slash command?
Thanks in advance,
Red
Not sure why left click on fubar isnt working.. I'll have to look into that. If you right click the button and open the menu, there should be an Open GUI option. If not, (i wasn't in game so i gave yopu the wrong slash command) you can do /cdt options to get the gui open.. However to do what you are wanting thru slash command, there isn't a way to at the moment.
The way to do it thru the menu, though is to open the menu, go to Group Settings, and then to Item Cooldowns, and select Delete Group. What this will do is not actually delete the ItemCooldowns Group, but it will disable it.
After it is disabled, reloadui and everything should be in the cdt group.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
No problem. I realise that anything with multiple cooldowns is going to be 'fun' to code elegantly.
I make it 3 cooldowns =)
I have too many trinkets for my own good =)
Ah, there it was :)
Seems the pulse bug it's not related to the rank after all, it happens when I SPAM a button, possibly hitting multiply buttons at once.
Are you able to reproduce this with only CDT running?
To be fair, it only bugs like once a day or so when you're in a pinch :)
To clarify, it bugs when I button mass.
Though it only bugs for the spell that I cast and a reload fixes it.
Yes, I'm able to reproduce with only CooldownTimers2 active.
HowTo: You really have to SPAM your buttons, and not just 1 button, multiply button. I did it with spamming QWERT all at once. Also the spell was already on cooldown, but not sure if this is important for reproducing.
Q = Counterspell
W = Strafe left
E = Move forward
R = Strafe right
T = Blink
Hope it helps.
That sounds more like an issue with the blizzard code. Addons don't just bug because of spamming, especially not with a specific case of multiple button spamming, so that has to be something in the C code, not the lua code (most likely in the keyboard stuff).... Sorry to say, because I hate going there myself, but since you can reproduce it easily, and I can't at all (not even using your method), could you report this on the blizzard bug forum?
But I can point out that there is an issue with this addon.
Found this in the CooldownTimers 2.0 thread and it's happening to be too and he said it just like I would so I'll just c/p it. :p
Where was this copied/pasted from? Any problems with the official release that result in a modified release need to be reported here so I can fix them, thus ending the modified release.. You have just reported it, and I will look into it, but I would like to get in touch with this person to let him know the proper method for reporting issues.
Typing my thoughts out as they come to me, so just ignore contradictory statements =)
The more I think about this, the more I don't wonder if maybe there is just something weird about either your machine, or your install of wow, or some combination of addons, and not what I had said previously. Perhaps another addon you are using is tainting the codepath somewhere. But then again you said that you are able to reproduce it with just cdt running... unless maybe it's something that cdt depends on that is doing it.. It's very strange that it would only happen when you spam several buttons at once, and even then only when you are really trying to reproduce it..
However, I do see some other glitches when spamming buttons, such as when my hearthstone is on cd, and I spam the 1 key (which right now is the reins for the new goats), I can see the hearthstone bar refresh every few keypresses. In other words, the bar will basically act like it is going to start over, and then drops back to what it was at before, all in less than a quarter of a second.. Literally it is a flash that is just over the threshold of how fast it would have to disappear for the human eye to not even register it. Maybe the problem isnt in the cdt code, but in the candy bar code.. I'm not sure when I will have time to check it out, but I will take a look. For now just hold off on reporting it to blizzard.
Looks like you found it and when I started looking at the dates of the replies there it also seems to be very old, no idea why it was so high in the General Addons list. Never the less it still isn't fixed so at least I did something else then bumping an old thread. :p
Would like to set it to the same ~30-50% alpha that i use for the rest of my UI.
ATM, no, but I could probably easily put it in..
http://video.google.com/videoplay?docid=-4615968462409357474&hl=en
Hope it helps a little, also I'll edit in a link to the bug report on the forums when I get that done :)
I would love it if you found the time/will to add it.
Unfortunately that doesn't help me reproduce it on my rogue, however I am able to unreliably reproduce it on my rogue now with ghostly strike, as I was farming motes a couple nights ago and noticed that the ghostly strike bar stopped pulsing but it started again after i reloaded. I'm trying to track it down now.
In trying to config CooldownTimers2 using the Rock config screen, I am getting this message in Bug Sack:
[2007/10/12 15:14:28-968-x2]: CooldownTimers2\Options.lua:1108: attempt to index field '?' (a nil value)
Anyone have any ideas on why?
Thanks in advance,
Red
Don't use rock to configure CDT, the layout of the GUI was designed for waterfall, so the only supported (working) config method is thru the GUI that you get when you left click the minimap or fubar icon, or type /cooldowntimers gui
Thanks in advance,
Red
Not sure why left click on fubar isnt working.. I'll have to look into that. If you right click the button and open the menu, there should be an Open GUI option. If not, (i wasn't in game so i gave yopu the wrong slash command) you can do /cdt options to get the gui open.. However to do what you are wanting thru slash command, there isn't a way to at the moment.
The way to do it thru the menu, though is to open the menu, go to Group Settings, and then to Item Cooldowns, and select Delete Group. What this will do is not actually delete the ItemCooldowns Group, but it will disable it.
After it is disabled, reloadui and everything should be in the cdt group.