Authors CurseForge

learn it :)
The problem is just that in the quest tooltip (daily or not) when I mouse over a quest title, an other tooltip should appear, but it doesn't because tomQuest doesn't find an anchor, and so it display a lua error.
The strange things is that with titan, tomQuest is able to find it. I have no idea why it works with one and not with the other, I just wonder maybe something isn't set the same way in the two LDB display, but what...

Chocolate is my fav LDB display addon
It's simple, nice, and light.

Thanks for this addon :)

Separate the options in order to make them LoD is a great idea.

At last, you should take a look at tomQuest2 ticket24, it seems that chocolate doesn't set an anchor, so tomquest is having lua error if use with chocolate but no error with titan for example.

XRS does, and can do only that (if you create only this bar)

Quote from Lanacan

Here is a raid shot... v14.1 (coming tomorrow hopefully) will update sThreatMeter to only show 6 bar (to keep if off the bottom of the screen without repositioning it) and an update to oUF_Lanacan.

http://s.wowinterface.com/preview/pvw23804.jpg

I like it, really. I read your ui page on wowi, but I cannon't find what did you use to display your raid health/name/target.

I use http://wow.curse.com/downloads/wow-addons/details/classicon.aspx
Using options /ci help you can remove class of party and target.

@StormFX : Thanks

Tankpoints (r100-nolib) and StatLogicLib (r203-nolib) too

I am working with disembed, and it seems that when I unistall an addon, every libs need for this addon are uninstall too, but without take care if it's need for an another addon...

If I uninstall without CC, the next time I will launch it, it will uninstall the libs too...

Am I the only one?

Thanks all :)

Hello,

I am looking at the blizzard cooldown frame, and I have few questions :

Using wowcompares I find into the BuffFrame.lua those lines :

name, rank, icon, ph, ph, duration, expirationTime = UnitBuff(unit, i, filter);
...
if ( icon ) then
...
if ( coolDown ) then
CooldownFrame_SetTimer(coolDown, expirationTime - duration, duration, 1);
...

If I look at the doc about UnitBuff I find (on wowwiki) :

duration
 Number - The full duration of the buff in seconds
expirationTime
 Number - Time the buff will expire in seconds

So, if I have a 30s buff that expire in 5s my parameters for CooldownFrame_SetTimer are

CooldownFrame_SetTimer(coolDown, (5 - 30), 30, 1);
so
CooldownFrame_SetTimer(coolDown, -25, 30, 1);

But if I look at Cooldown.lua

function CooldownFrame_SetTimer(self, start, duration, enable)
 if ( start > 0 and duration > 0 and enable > 0) then
  self:SetCooldown(start, duration);
  self:Show();
 else
  self:Hide();
 end
end

the start is always < 0, so where am I wrong? ???

Thanks in advance

ps: Thanks to move the thread into "Lua Code Discussion", and remove the "e" of "frome" in the title... sorry :p

Thanks

Quote from Xinhuan

If a person is in a vehicle, referring to their pet would refer to the vehicle. That is, "partypet2" would be a vehicle.

Same for player, or use "vehicle" ?

Thanks, I can't test right now, but if it works, what about the party's vehicule?

Hello, I am trying to make some changes for my UnitFrame, and I have a few questions about vehicules.

When I am in a vehicule, I'd like to know the current and max hp of it.

I guess it something like that :

if (UniteInVehicle("player")) then[INDENT]local vehicleUnit = [COLOR=Red]???[/COLOR] -- here is my problem
local cur = UnitHealth(vehicleUnit);
local max = UnitHealthMax(vehicleUnit);
...
[/INDENT]end

I am sure it's nothing, but I can't find it here or on wowwiki.

Thanks in advance.

768 is not a 2power, I think that's why (but not sure)
try with 2 tga
1024*512 + 1024*256

form Guide: WoW Compatible Images
http://forums.wowace.com/showpost.php?p=259409&postcount=1

Quote from StormFX

The height and width of the image must be a power a 2

RIP Visor, I miss you so much :'(

Altought it causing taint, I am still using it because ... it's still working, and I have no display problem with it.

I prefer more more more (...) Visor than moveAnything, for me it's more powerfull et use less memory.

Ok it's not friendly user the first time you use it, but no so hard too.

If we could find what is causing the taint, that will be perfect :)