Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
@ Xara: The easiest way to do this, is to modify the Default alpha template for combat and out of combat.
Default-Combat:
Make sure every bar to the right is at 1.
1.00 1.00
....
0.0 1.00
Default-Non combat:
The top lines should have the values:
1.00 0.0
0.99 1.0
....
and the rest should be what ever you feel like :) I'm using this same setup for my bars at the moment.
@ Shanyu: I've added the toggle binding, you'll find it under Key Bindings => mHud => Enable or disable mHud.
@ razoon: The bars will now go gray if someone else has tagged the mob.
@ Xara: LibDogTag-3.0 messed with outlining last time I tried, not sure if 2.0 does to. But I'll see if I can squeeze inn the outlining flags.
As for the casting bar, I haven't done channeling bars in some time, and DogTag support for cast isn't perfected yet. It's a lot of hazel to add custom text for casting.
Thanks for making this nice hud, I've recently checked a lot of them, but this seems really nice :) One question though, when I make a text for a bar, I can controll the x- and y-position via faders. I'm not sure if I'm just clumsy, but I need finer control over that than I can get. For example, right now I can't get a certain text to a y-position between 0 and 40, the fader just jumps between those 2 values. I'd love e.g. to have an input box, where I can just type the value I need. Or is there any other way to have a better control?
Also, how can I find out what the various modules do? Some are easy to guess, but others are not (at least for me ^^). The README doesn't contain that info :( I also don't get what "templates" are supposed to be, and how to modify them, can anybody point me in the right direction?
And just for the record, I'd like support for dog tags 3.0 as well :)
Pyrates: If you click the text by the sliders, you can edit it by punching in numbers :)
There should be some explanations to the templates on the last few pages of this thread, GL =)
I tried to implement LibDogTag-3.0 in some personal unit frames, but I found it to inefficient in concern to mem/cpu, that was quite a few months ago, might be improved by now, but I haven't relay had the time.
Hi Merl!
Thanks for your work. Like Pyrates, I'd like to see DogTags-3.0 in your addon, as it has some nice features, DogTags-2.0 don't have, like the AuraDuration(). If you're concerned for mem/cpu, maybe its possible to make it as a seperate module or like the threatbar even a seperate addon.
Hi again.
I might have found a bug. When you enter a long DogTag, the editfield can't take the complete DogTag and cuts it down to 256 chars. I have no clue if this is an internal limitation by blizzard or of the editfield. But if you could increase the 256 characterlimit, that would be very nice.
Hi again.
I might have found a bug. When you enter a long DogTag, the editfield can't take the complete DogTag and cuts it down to 256 chars. I have no clue if this is an internal limitation by blizzard or of the editfield. But if you could increase the 256 characterlimit, that would be very nice.
I just use the Ace3 GUI, don't know where the limitation lies, but it's prob. a blizzard limitation on the input fields.
I might add a module with DT3, but don't hold your breath.
I might add a module with DT3, but don't hold your breath.
Hi, that would be very very useful, as DT2 doesn't support Threat-2.0.
And another request (sorry^^), is it possible to add an option for raidsymbols?
On a sidenote, i made a module which hides the blizzard standard frames, but i'm having some trouble with the config. i copied the config.lua from the alphgradient module and changed it accordingly, but i dont geht any config options. only en-/disabling the module does work. if you like, i could send you the module, its pretty simple.
You prob need to change the keys of the tables, if they are the same, they get overwritten by the modules you copied the code from. I can't remember how I implemented the config part, but it might suppress errors, thus leaving you with nothing happening and no feedback.
GL though =)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Default-Combat:
Make sure every bar to the right is at 1.
1.00 1.00
....
0.0 1.00
Default-Non combat:
The top lines should have the values:
1.00 0.0
0.99 1.0
....
and the rest should be what ever you feel like :) I'm using this same setup for my bars at the moment.
thanks, I really had to look 2 times over the whole config dialog to
find the template editing. It's kinda hard to find even if you know
it's there...
Now I've got another feature request:
Font Outline
How about the Casting Bar support?
@ razoon: The bars will now go gray if someone else has tagged the mob.
@ Xara: LibDogTag-3.0 messed with outlining last time I tried, not sure if 2.0 does to. But I'll see if I can squeeze inn the outlining flags.
As for the casting bar, I haven't done channeling bars in some time, and DogTag support for cast isn't perfected yet. It's a lot of hazel to add custom text for casting.
Ref: http://www.wowace.com/forums/index.php?topic=12832.msg203811#msg203811
Thanks for making this nice hud, I've recently checked a lot of them, but this seems really nice :) One question though, when I make a text for a bar, I can controll the x- and y-position via faders. I'm not sure if I'm just clumsy, but I need finer control over that than I can get. For example, right now I can't get a certain text to a y-position between 0 and 40, the fader just jumps between those 2 values. I'd love e.g. to have an input box, where I can just type the value I need. Or is there any other way to have a better control?
Also, how can I find out what the various modules do? Some are easy to guess, but others are not (at least for me ^^). The README doesn't contain that info :( I also don't get what "templates" are supposed to be, and how to modify them, can anybody point me in the right direction?
And just for the record, I'd like support for dog tags 3.0 as well :)
There should be some explanations to the templates on the last few pages of this thread, GL =)
I tried to implement LibDogTag-3.0 in some personal unit frames, but I found it to inefficient in concern to mem/cpu, that was quite a few months ago, might be improved by now, but I haven't relay had the time.
Thanks for your work. Like Pyrates, I'd like to see DogTags-3.0 in your addon, as it has some nice features, DogTags-2.0 don't have, like the AuraDuration(). If you're concerned for mem/cpu, maybe its possible to make it as a seperate module or like the threatbar even a seperate addon.
I might have found a bug. When you enter a long DogTag, the editfield can't take the complete DogTag and cuts it down to 256 chars. I have no clue if this is an internal limitation by blizzard or of the editfield. But if you could increase the 256 characterlimit, that would be very nice.
I just use the Ace3 GUI, don't know where the limitation lies, but it's prob. a blizzard limitation on the input fields.
I might add a module with DT3, but don't hold your breath.
Hi, that would be very very useful, as DT2 doesn't support Threat-2.0.
And another request (sorry^^), is it possible to add an option for raidsymbols?
On a sidenote, i made a module which hides the blizzard standard frames, but i'm having some trouble with the config. i copied the config.lua from the alphgradient module and changed it accordingly, but i dont geht any config options. only en-/disabling the module does work. if you like, i could send you the module, its pretty simple.
GL though =)