The downside is that you'll have to make sure that the item in question is "known" to the client. If you don't mind adding a lib dependency to your addon, then you can use LibRangeCheck-2.0 and let it handle the details for you. Check the API docs for more info.
cheers,
mitch
ps: it won't help with cone direction detection, and I don't think it's even possible to do for enemy units.
Is is possible to put a static width on the plugins?
Hi,
Currently you cannot set a static width, but you can set the maximum width with the Max text width plugin option and you can set the Shrink threshold plugin option to tell Bazooka not to make the plugin smaller unless the plugin text shrinks by this amount. Setting this to a high value will effectively make the plugin never shrink, so it'll settle on the Max text width (if it ever grows that large).
If you use _G only to access globals, it's easier to catch accidental global access (usually a typo) with "luac -p -l x.lua |grep GLOBAL" as you should only see _G in that output.
I dont know if this is just impossible, but i have a problem with the 40y range check. This range check only works for people in my raid/group. Other ranges like 28y work flawless.
Just a quick advice to those that consider switching to Bazooka: the current release (1.7.0) has a nasty bug with plugin placement configuration. The latest alpha on wowace is updated for 3.3 and should work, but I couldn't yet test it on live, so I haven't tagged it yet. Hopefully a proper release will be available later today.
cheers,
mitch
Edit: I just tagged a new release, Grum said the alpha works, blame him if it doesn't :)
Or you could just be trendy and switch to an LDB based display addon (I personally recommend Bazooka for obvious reasons :) and replace your current FuBar plugins with LDB plugins.
You can use Fubar2Broker for the few FuBar plugins you don't find suitable LDB based replacements for.
(yes, Fubar2Broker is the one that converts old FuBar plugins to LDB, and Broker2Fubar does the reverse, Networkerror gave the wrong name but the right link :)
Thanks for the tickets, I think I fixed all of them, please check and report back if something's amiss. Regarding the statusbar textures, I don't think that's a good idea, but I might experiment with it a bit.
I've created a couple of tickets for some minor things I've seen, and I've also got a question.
Would it make sense to use statusbar textures from LibSharedMedia rather than background textures?
What bugs me is a friendly will fade at a range of 8 yards on my hunter but a hostile will fade at 28 yards meanwhile my attack distance is 35 yards on all hostiles. Is there any way to setup a range setting that is not dependant on hostility of the thing the frame is showing?
Hello,
I've created an alternative range fader for PitBull4 based on LibRangeCheck-2.0. It might work out for you: PitBull4_RangeFader2.
(It's not yet approved, dunno if you can grab it or not at this stage)
Hey, great job! Clean interface and works great! I do have one odd request: Can you have it default to the "Default" profile? If I notice any issues, I'll let ya know. And thank you!
0
cheers,
mitch
0
You could use IsItemInRange() with a suitable item ID. I use the following items in LibRangeCheck:
The downside is that you'll have to make sure that the item in question is "known" to the client. If you don't mind adding a lib dependency to your addon, then you can use LibRangeCheck-2.0 and let it handle the details for you. Check the API docs for more info.
cheers,
mitch
ps: it won't help with cone direction detection, and I don't think it's even possible to do for enemy units.
0
Hi,
Currently you cannot set a static width, but you can set the maximum width with the Max text width plugin option and you can set the Shrink threshold plugin option to tell Bazooka not to make the plugin smaller unless the plugin text shrinks by this amount. Setting this to a high value will effectively make the plugin never shrink, so it'll settle on the Max text width (if it ever grows that large).
cheers,
mitch
0
cheers,
mitch
0
cheers,
mitch
0
if type is 'spell', then id is no longer the spellbook index, but the spellId.
cheers,
mitch
0
0
Take a look at PitBull4_RangeFader2, maybe you'll have better luck with that.
cheers,
mitch
0
Just a quick advice to those that consider switching to Bazooka: the current release (1.7.0) has a nasty bug with plugin placement configuration. The latest alpha on wowace is updated for 3.3 and should work, but I couldn't yet test it on live, so I haven't tagged it yet. Hopefully a proper release will be available later today.
cheers,
mitch
Edit: I just tagged a new release, Grum said the alpha works, blame him if it doesn't :)
0
You can use Fubar2Broker for the few FuBar plugins you don't find suitable LDB based replacements for.
(yes, Fubar2Broker is the one that converts old FuBar plugins to LDB, and Broker2Fubar does the reverse, Networkerror gave the wrong name but the right link :)
cheers,
mitch
0
Hi,
Did you need to adjust the positioning with the "Tweaks" or the 1 pixel gap just disappeared?
0
Thanks for the tickets, I think I fixed all of them, please check and report back if something's amiss. Regarding the statusbar textures, I don't think that's a good idea, but I might experiment with it a bit.
cheers,
mitch
0
Hello,
I've created an alternative range fader for PitBull4 based on LibRangeCheck-2.0. It might work out for you: PitBull4_RangeFader2.
(It's not yet approved, dunno if you can grab it or not at this stage)
cheers,
mitch
0
0
I switched to the Default profile thing in the latest alpha (r73). I'll tag a release in a day or two if nothing else comes up worth fixing.
cheers,
mitch