nUI_Button.lua

[Astrocanis]

Received this error the first time I targeted something:

Interface\Addons\nUI\Bars\nUI_Button.lua:1196:Usage:UnitIsUnit("unit","otherUnit").

Pressing "Okay" did not resolve it - the error continued.

[Xrystal]

Hmm, sounds like that split second target is locked kinda thing. Anything else mentioned after that line to shed some more light on the problem ?

[spiel2001]

Hmmm... that's a really odd one. The only way that error could occur is if an aura on the target didn't have anyone who cast the aura. o.O

In any event, I've added a trap for it. You can fix it yourself until I get the next patch out by editing [ Interface > AddOns > nUI > Bars > nUI_Button.lua ] and going to line 1192 where you'll see the following segment of code... add the new line (that's in blue) to the rest of the section.

if  aura.end_time
and aura.caster
and aura.end_time > proc_time
and aura.name == overlay.spellStatus.name
and aura.rank == overlay.spellStatus.rank                    
and UnitIsUnit( aura.caster, "player" )
then 
    overlay.spellStatus.remains = aura.end_time - proc_time;
    overlay.spellStatus.color   = { r=0, g=1, b=1 };
    break;
end

[Xrystal]

Is it possible that the person that cast the aura left the raid and thus the addon couldn't identify the owner ?

I know auras eventually get removed when people respec and possibly leave the raid but maybe it was one of those split second tests that went wrong.

[spiel2001]

Yeah -- I'm guessing it's something like that. The "and aura.caster" addition to that conditional should solve the problem since Lua uses short-circuit logic rules. The "and aura.caster" would resolve to false and kill the test before it gets to the UnitIsUnit( aura.caster, "player" ) test.

[Xrystal]

rofl .. Im still trying to figure out those weird and/or combinations .. I've been doing simple conditionals as I know how they work

[Astrocanis]

Thanks, Scott. I'm going to give it a try (when the maintenance is over =P).

[spiel2001]

Originally Posted by Xrystal rofl .. Im still trying to figure out those weird and/or combinations .. I've been doing simple conditionals as I know how they work

~lol~

Yeah... took me a bit to get my head around that at first. If you program in C/C++ then they're much like the C tertiary statements...

int i = value > 0 ? 1 : 0;

In Lua that would be done like this

local i = (value > 0) and 1 or 0;

The rule for conditional processing in Lua is that the first condition that resolves the statement stops processing of the statement. Since any condition that resolves true makes an "or" true, the (value > 0) and 1 portion of the statement is true, so the "or" is already resolved and the statement stops processing thus assigning 1 to i. If (value > 0) is false, then false and 1 is also false, so the statement continues past the "or" and returns 0. Heady stuff, but really powerful.

The same is true in traditional conditional processing...

if a > 0
and b > 0
and c > 0
then doSomething()
end

If (a > 0) then the conditon test stops dead right there and never even bothers looking at the (b > 0) or (c > 0) part of the condition. This can make your code very efficient if you order your conditions to start with the most likely or easiest to test conditions first since that allows skipping all the rest of the tests if those conditions aren't met.

[fred]

Still solo...nothing special.Guess I'm just good at breaking stuff

[2009/06/02 23:18:51-6-x26]: nUI-5.03.06 (Dev)\Bars\nUI_Button.lua:1218: Usage: UnitIsUnit("unit", "otherUnit")
nUI-5.03.06 (Dev)\Bars\nUI_Button.lua:1218: in function <Interface\AddOns\nUI\Bars\nUI_Button.lua:1155>

---

[Astrocanis]

Scott, made the change to the lua file, but the problem is still cropping up. Sorry to bother you like this.

After a while I get the "Addons have generated a large number of ..." disable message.

[Xrystal]

Ah another one of these .. sheesh .. played for hours today and had no errors whatsoever .. rofl, what are you guys doing to this ?

[spiel2001]

Is it still that exact same error?

[ Interface\Addons\nUI\Bars\nUI_Button.lua:1196:Usage:UnitIsUnit("unit","otherUnit") ]

Or is it something else? Are there *any* other error messages besides that one? The fact that no one else is screaming about this makes me believe it's a conflict issue.

[Xrystal]

psst .. someone else did report it Scott in another post

[spiel2001]

Yeah -- this really puzzles me as I've *never* seen this error. Gotta figure out what's causing it.

[spiel2001]

Yeah -- I just saw Fred's post, too.

EDIT: I've merged them into one thread so as not to be answering the same questions in two places.

[fred]

No other errors for me.I'll see if I can upload my mod list.

[spiel2001]

I'd be curious to know if you can force it to happen or figure out the exact sequence that reliably causes it to happen. Then, if you can, if you disable all mods except nUI, does the problem go away or is it still there?

[Xrystal]

Hmm, was it the first time you targetted something when you first logged in ?

Let me test that out. I think I heard a noise a couple of times tonight while playing about on other servers while waiting for our one to come up ... which it did at about midnight Pacific so pretty much a dead server


Edit: Nope .. logged in fresh on a toon and clicked on about 10 things, myself, my target, my targets target (in essence all me. Then targetted humanoids, animals, npcs. No problems whatsoever.

Went through bug logs but nothing with nUI in there that I might have missed.

[Lackin]

Everytime i get on a mount of any kind i get an error

[Lackin]

And another 0ne And this error is if i click on anything it pops up so i have to not click on anything and if i click on something to kill it it pops up