1. LibQTip-1.0 r104 spawns an error as long as any other addon are loaded, that use an older version of LibQTip. For example:
LibQTip-1.0-21 (Testy):603: attempt to index field 'scrollChild' (a nil value)
LibQTip-1.0-21 (Testy):618: in function <Interface\AddOns\Testy\libs\LibQTip-1.0.lua:616>
LibQTip-1.0-21 (Testy):736: in function <Interface\AddOns\Testy\libs\LibQTip-1.0.lua:638>
(tail call): ?:
RepairBroker-3.1.0 Beta4\RepairBroker.lua:266: in function `RenderEquippedDurability'
RepairBroker-3.1.0 Beta4\RepairBroker.lua:247: in function <Interface\AddOns\RepairBroker\RepairBroker.lua:214>
2. Once all other addons using LibQTip have been deactivated, no more errors come up - until this is reached:
local y, x = cell:GetPosition()
print("The cell is on line "..y", column "..x)
I get the following error for the print line:
Testy-TEST\Testy.lua:27: attempt to call local 'y' (a number value)
<string>:"safecall Dispatcher[4]":4: in function <[string "safecall Dispatcher[4]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[4]":13: in function `?'
CallbackHandler-1.0-3 (Ampere):91: in function `Fire'
LibQTipClick-1.1-3 (Testy):49: in function <Interface\AddOns\Testy\libs\LibQTipClick-1.1.lua:49>
And finally 3., because I'm a noob when it comes to coding:
I tried to change the tooltip via SetCell() from the function that handles the mouseclick, but I couldn't find the right way to use SetCell() to get it working. How exactly would I have to change the tooltip from there?
@neolith:
I'm not experiencing that issue, and haven't seen any posts about it in this thread. Have you tried removing your ButtonFacade saved variables? Deleting and reinstalling ButtonFacade? Logging in with only ButtonFacade installed?
I've deleted the SV several times, to no success. I'll try a clean install of BF as well next time I log on.
I'm sorry if this came up before, but I couldn't find any info about this:
The testbar does not stay deacitvated. Whenever I log into a char, it shows again and has to be removed.
A donations-only version of WAU that has ads removed. There was certainly a demand before this happened, and I think many users would willingly "buy" an adfree version over using an old or hacked one. I know the timing might seem bad, but the demand is there.
this is very sad, the idea was perfect for me, and seems like noone else going to pick it up
i either end up learning lua or - dunno, really
i am lost. i just cant imagine the gameplay with this addon.
I haven't played much WoW lately and did not have any time to get to work on Litmus at all. Sorry about the lack of updates - I'll try to get back to it in the new year.
[2007/09/27 20:24:23-982-x4]: AuldLangSyne-r49802\Fu\Fu.lua:431: RollCall-1.0: Argument #2 must be "NAME", "LEVEL", "CLASS", "ZONE", "RANK", or nil, got "ONLINE".
Ace2\AceLibrary\AceLibrary.lua:133: in function `error'
RollCall-1.0-34869 (AuldLangSyne):379: in function `GetIterator'
AuldLangSyne-r49802\Fu\Fu.lua:431: in function `OnTooltipUpdate'
FuBarPlugin-2.0-48629 (Prat):366: in function `runChildren'
Tablet-2.0-49630 (Prat):2355: in function `children'
Tablet-2.0-49630 (Prat):2399: in function `Open'
Tablet-2.0-49630 (Prat):2533: in function <Interface\AddOns\Prat\libs\Tablet-2.0\Tablet-2.0.lua:2527>
FuBarPlugin-2.0-48629 (Prat):415: in function <...AddOns\Prat\libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:414>
FuBar plugin doesn't work properly (no tooltip). I get the above on every mouseover. Hope this hasn't been postet before, but using the search I didn't find anything...
it seems like that color error happens with draenei shamans only.
I thought that at first, too. But it happens way more on my warlock than on the shaman I created for testing. Could be there always was a shaman in my group though.
Right now I tend to believe that RAID_CLASS_COLORS is buggy.
Unfortunately I had no free time at all the last weeks, so sorry for the lack of updates on this...
i have a request then - can you add option to turn Litmus off during BGs?
i use it only in PVE or Arena, and doubt anyone really need it in AV.
You can do that with
/litmus standby
to switch the addon on/off.
I have been able to produce the error myself now - funny thing is that I cannot do it on purpose. Sometimes it happens (a lot) and sometimes it doesn't.
I'll have to do a bit more testing with alternate code.
i currently can't get rid of showing pets even with it turned off :(
happens in battlegrounds and rarely in outdoor raids.
i would be most greatful if you can correct this one.
i think i can reproduce it with bugsack/grabber installed, just if you need it.
I'll look into it this weekend.
Did you change the textcolor for Litmus or are you using the default one? Also does this error come randomly or can you make it happen through certain actions?
any plans on updating this one?
getting some nasty bugs in raids (especially BGs)
will post complete log next time i catch it
litmus is something my interface will barely survive without :(
Please post all the errors you are getting here and I'll see what I can do.
I rarely play my druid any more and I never visit BGs so it's quite possible that the latest patches broke something that I'm not aware of.
Just a thought but how about adding a toggle to not place icons on friendlies. I find it kind of annoying seeing the icons jump around all the time lol. I changed it in my local copy but haven't tested it yet. Nice work:)
If I'd do that then the addon would stop working.
See, there is no command that tells the game to not show RTI number X any more. You can only tell it to not show any RTI on a targeted unit. So I have to cheat a little to achieve that effect. Once the char that you set in FromAViewToAKillFu to set the dynamic RTI loses his target there is no ordinarc way to delete the RTI on his former target. So the addon assigns that RTI to a Unit not having any and then quickly deletes it on the next possible frame. Hence the jumping. Unfortunately a little server lag can slow down this process so that it's noticable better. Preventing to let the RTIs show on friendly chars also prevents them to get deleted from lost targets.
0
1. LibQTip-1.0 r104 spawns an error as long as any other addon are loaded, that use an older version of LibQTip. For example:
2. Once all other addons using LibQTip have been deactivated, no more errors come up - until this is reached:
local y, x = cell:GetPosition() print("The cell is on line "..y", column "..x)I get the following error for the print line:And finally 3., because I'm a noob when it comes to coding:
I tried to change the tooltip via SetCell() from the function that handles the mouseclick, but I couldn't find the right way to use SetCell() to get it working. How exactly would I have to change the tooltip from there?
0
Yeah, I picked the wrong thread - it was late at night. Sorry about that.
Thank you for your answer, I'll give it a try. :)
0
0
I've deleted the SV several times, to no success. I'll try a clean install of BF as well next time I log on.
0
The testbar does not stay deacitvated. Whenever I log into a char, it shows again and has to be removed.
0
I'd pay for an adfree version. :)
0
I haven't played much WoW lately and did not have any time to get to work on Litmus at all. Sorry about the lack of updates - I'll try to get back to it in the new year.
0
FuBar plugin doesn't work properly (no tooltip). I get the above on every mouseover. Hope this hasn't been postet before, but using the search I didn't find anything...
0
I thought that at first, too. But it happens way more on my warlock than on the shaman I created for testing. Could be there always was a shaman in my group though.
Right now I tend to believe that RAID_CLASS_COLORS is buggy.
Unfortunately I had no free time at all the last weeks, so sorry for the lack of updates on this...
0
I do - looking at working addons is the best way to learn how to work with the framework.
0
You can do that with
to switch the addon on/off.
I have been able to produce the error myself now - funny thing is that I cannot do it on purpose. Sometimes it happens (a lot) and sometimes it doesn't.
I'll have to do a bit more testing with alternate code.
I'll look into it.
0
0
I'll look into it this weekend.
Did you change the textcolor for Litmus or are you using the default one? Also does this error come randomly or can you make it happen through certain actions?
0
Please post all the errors you are getting here and I'll see what I can do.
I rarely play my druid any more and I never visit BGs so it's quite possible that the latest patches broke something that I'm not aware of.
0
If I'd do that then the addon would stop working.
See, there is no command that tells the game to not show RTI number X any more. You can only tell it to not show any RTI on a targeted unit. So I have to cheat a little to achieve that effect. Once the char that you set in FromAViewToAKillFu to set the dynamic RTI loses his target there is no ordinarc way to delete the RTI on his former target. So the addon assigns that RTI to a Unit not having any and then quickly deletes it on the next possible frame. Hence the jumping. Unfortunately a little server lag can slow down this process so that it's noticable better. Preventing to let the RTIs show on friendly chars also prevents them to get deleted from lost targets.