If you only want 'Smart' for hiding the 0, then try:
[MissingHP:VeryShort:Color(ff7f7f):Hide(0)]

got it working thanks alot. it wouldnt work hide at the end, however i tried
[MissingHP:Hide(0):VeryShort:Color(ff7f7f)] and it worked.

Not sure if anyone else has had this problem.
There's just a chance I'm not seeing something amazingly simple.

I love Pitbull. It's amazing. But for my raid setup I don't need groups 6-8. I'm not sure what I'm doing wrong, but how do I have it stop showing those groups?

The option does exist in the menu, but for some reason it doesn't work (no changes happen when you click any of the groups). In the end I had to edit the SavedVariables\PitBull.lua and set the Group6-8 show tags to false.

It has the same option as Grid to only show "25 Man Style Raids", and it works good for me at least.
Im at work and cant direct you to what area in the config menu it is, but can get back to you during the night.

I'll try to scrounge for it until then.
Thanks for the heads up.

If you havent found it, iirc its under general settings somewhere, and you have to "Untick" group 6 to 8.

Hope my vauge information helps you.

Pitbull seems to have been updated a lot in the past week and is working fine now. Not sure about the memory leak but I'm pretty sure it has been fixed.

Last week is another story though as it was completely messed up for a few days.

I just installed Pitbull today to try it out in place of Xperl but I started getting a weird error when I mouse over Grid now;

Interface\FrameXML\GameTooltip.lua:74:Usage:Gametooltip:SetOwner(frame)

Anyone have any idea what it is/how to fix it?

I'm getting the same error. I'm not completely sure it's just Pitbull causing it. I'm using Tinytip also and any time I mouse over any pitbull frame the error pops up and I don't get a tooltip like I normally would. I updated both mods last night but was still getting the error.

The original author of TinyTip stopped developing the ace2 version of the mod months ago, no idea if he even still plays wow. He moved his mod to no framework and hosted on google code. 2.2 changed how gametooltips work, it's likely you'll need to ditch TinyTip for a different Tooltip mod.

Try CowTip, you can customize it so it looks exactly like TinyTip did or however you want.

Running a few tests tonight and I see Pitbull is using 5Mb of memory (1.2 Ace, 3.8 Pitbull) just for 3 unitframes, player, target and targets target, only modules used are hp, combatfade and powerbar, also bearing in mind the latter two are 80% hidden
Never has been or never will be an efficient mod by the looks of things

PitBull no longer uses Ace, so...yeah. Did you mean 1.2MB for Rock? If you're using embedded libraries - and if you don't know what that means, then you probably are - then PitBull and Rock are sharing 3.8MB total. Which isn't great, but it isn't bad either.

Yeah you're right, its going to be 3.3Mb for Pitbull and 1.7Mb for Ace2, not Ace

I don't see how ~5MB for 3 unitframes with only 3 modules loaded is efficient, the general user consenus is Ace/Rock based mods should be more efficient compared to other untframe mods, this doesn't seem to be the case..

As an example, I also run RDX with a huge amount of unitframes, individual boss desktops, bossmods, Lua error monitor, inbuilt WWS, Swstats/Mobhealth integration, Window creator etc etc and never reach above 4Mb.
In fact, building identical unitframes with RDX gained me no increased memory usage at all

If Swstats/Recount were as inefficient as Pitbull (considering their huge amount of data collection) no one would touch them with a barge pole

When I right click on my focus frame, Pitbull always opens Rock, which I dont want to, since I want to click cast something. Anyonen know how to stop Rock from showing? And can I even use Clique for Pitbull's focus frame? Since there's not focus frame option in Clique's options...

I came across a new problem today.

I found I was unable to heal party pets using Clique. I'm not sure if this is a Pitbull issue or a Clique issue, but the rest of my Pitbull frames are working fine and I can click-cast to my hearts content on them. But nothing on the pet frames.

It's not exactly a serious problem, but I'm curious if any one has come across the same issue and if it's been resolved. The issue didn't exist before the latest patch.

I was getting this as well during our arena matches last night. Mine was about 50/50 if they would work or not. I forgot to play around with my mods afterwards to nail it down, so I'll do that next I log in.

Try updating Clique to r88. I had the same issue with r87.

Brilliant. It worked. Thanks for the heads up.

This has been annoying the living out of me since I started using PitBull. How do you get the bars, such as the Health and Power bar, to not constrain or resize each other when you resize one?

Altho this seems like real basic sh*t since everyone and my grandmother seem to have it working, I don't. Sorry.

How do I get the aura's to show, I am using someone else's saved variables and I believe they disabled the aura function. If this is the case how do I re-enable them?

On a similar note, I have just updated to using pitbull since the 2.2 patch. However, while I enjoy the modular use and the amount of info/configuration at my fingertips I do NOT like having to adjust it every time I log on. I am not switching profiles or anything, yet if I log out of wow (after having saved a profile, and most of the individual frame layouts) 80% of the settings I have adjusted are wiped out.

A searched this thread and there was only one other post in reference to this problem. But it was about switching profiles mid game, not about a profile being lost when he logged out. Even after I go back to each individual frame and manually set them to the saved mini-profiles from before - size, aura, icons (especially the good-for-nothing PVP icon),etc are reset to the default settings.

If there is no way to fix this problem I am going to have to dump the mod even though I really enjoyed it for the hour or so I was able to play it when my optimal settings had just been set up.