I've some additional info on the problem, on the char where RBM is malfunctioning, which is on a seperate account, the following errors are given:
Addon action is blocked, RBM tried to call on a protected function: 'Worldframe: ClearAllPoints()'. <in C Code>. In function 'ClearAllPoints'
RBM-2.0.8.$Rev: 77624 $\Core.lua:910: in function <Interface\Addons\RBM\Core.lua:894
and:
Addon action is blocked, RBM tried to call the protected function 'WorldFrame:SetPoint()'.
RBM-2.0.8.$Rev: 77624 $\Core.lua:912: in function
<Interface\AddOns]RBM\Core.lua:894
Buggrabber eventually stops capturing these errors as they happen more frequently than 60 times per minute.
EDIT: The errors actually occur more than 20 times per second.
At the moment i'm using abilitywatch on two different toons played from the same computer. The problem i'm currently having is that on one toon the warnings result in a shake and flash, which is the desired result. On the other toon i'm unable to get this result. There simply is nothing happening when those abilities that are flagged in the warning section are being used.
I can't for the life of me figure out the problem.
I have a question regarding abilitywatch, i may have missed it but i would like to color the cooldowns/casts in the color partaining to relevant class. Such as Iceblock Cooldown is light blue as that's the color associated with Mages. If it's already possible I apologize for posting, but I've been unable to find it.
Also, I was wondering if the :: Cooldown :: part can already be removed from the label. It takes up so much space on the bar. Another thing that boggles me is the fact that after experiment with the Theme Settings I'm somehow confronted with a random number showing up after the :: Cooldown :: part of the label, ie 953. I've solved this by deleting the frame and creating a new one without touching the theme settings. These scare me now.
I hope this helps, I've found a way arond the problem by unselecting the 'Filter by Category' option, this allows proper saving of settings. If it's selected the category goes to AbilityWatch again and I have to manually reset the filters.
Also, is the ':: Cooldown' part of the label removable currently?
Firstly, the addon is on it's way to brilliance. Good job.
I'm having a problem I'd like to ask a question about. Currently there seems to be a bug with my various frames not saving settings. For example, I have a frame named Drums for the Drumwatch rotation, however, when relogging the settings are changed to AbilityWatch. I of course use seperate frames for those, but everything seems to display AbilityWatch after relogging.
I read that someone else had a similar problem with another plug-in, I couldn't find a solution to his problem.
Another question I have is with regard to the possibility of have the ':: Cooldown' part of the Label removed, is this possible currently?
i've just discovered this addon and am quite liking the versatility and feel of it. i have a problem however, none of the frames, test or plugin (drum watch is the one care most about atm) will show. I can however create a custom bar which specific parameters which will pop up and have thus simulated how drum watch should work with some parameter juggling using the word 'drums'. for the life of me i can't seem to get any bars except those i've made myself to show up, just to repeat, these include debuff/buff timers, cooldown watch and test suite. buggrabber shows nothing with regards to these errors. i'm expecting a conflict somewhere, but i just have no idea where to look.
EDIT: to give some, perhaps relevant, information: drum watch does announce in text to party when cd's are ~30 secs away from being up and also does the random test and announce in /p. it just doesn't show the bars. i've also selected the buffs to show on the long and short cooldown bars, but neither actually shows it.
0
Addon action is blocked, RBM tried to call on a protected function: 'Worldframe: ClearAllPoints()'. <in C Code>. In function 'ClearAllPoints'
RBM-2.0.8.$Rev: 77624 $\Core.lua:910: in function <Interface\Addons\RBM\Core.lua:894
and:
Addon action is blocked, RBM tried to call the protected function 'WorldFrame:SetPoint()'.
RBM-2.0.8.$Rev: 77624 $\Core.lua:912: in function
<Interface\AddOns]RBM\Core.lua:894
Buggrabber eventually stops capturing these errors as they happen more frequently than 60 times per minute.
EDIT: The errors actually occur more than 20 times per second.
0
I can't for the life of me figure out the problem.
0
Also, I was wondering if the :: Cooldown :: part can already be removed from the label. It takes up so much space on the bar. Another thing that boggles me is the fact that after experiment with the Theme Settings I'm somehow confronted with a random number showing up after the :: Cooldown :: part of the label, ie 953. I've solved this by deleting the frame and creating a new one without touching the theme settings. These scare me now.
0
0
I hope this helps, I've found a way arond the problem by unselecting the 'Filter by Category' option, this allows proper saving of settings. If it's selected the category goes to AbilityWatch again and I have to manually reset the filters.
Also, is the ':: Cooldown' part of the label removable currently?
0
I'm having a problem I'd like to ask a question about. Currently there seems to be a bug with my various frames not saving settings. For example, I have a frame named Drums for the Drumwatch rotation, however, when relogging the settings are changed to AbilityWatch. I of course use seperate frames for those, but everything seems to display AbilityWatch after relogging.
I read that someone else had a similar problem with another plug-in, I couldn't find a solution to his problem.
Another question I have is with regard to the possibility of have the ':: Cooldown' part of the Label removed, is this possible currently?
0
i've just discovered this addon and am quite liking the versatility and feel of it. i have a problem however, none of the frames, test or plugin (drum watch is the one care most about atm) will show. I can however create a custom bar which specific parameters which will pop up and have thus simulated how drum watch should work with some parameter juggling using the word 'drums'. for the life of me i can't seem to get any bars except those i've made myself to show up, just to repeat, these include debuff/buff timers, cooldown watch and test suite. buggrabber shows nothing with regards to these errors. i'm expecting a conflict somewhere, but i just have no idea where to look.
EDIT: to give some, perhaps relevant, information: drum watch does announce in text to party when cd's are ~30 secs away from being up and also does the random test and announce in /p. it just doesn't show the bars. i've also selected the buffs to show on the long and short cooldown bars, but neither actually shows it.