Get an Epic Experience with Premium

PitBull Unit Frames 4.0

Unit Frames Login to Add Favorites
  • 44 Likes
  • World of Warcraft
  • 11,822 Monthly Downloads
  • Supports: 5.4.0
  • 3,439,048 Total Downloads
  • Updated 09/30/2013
  • Created 08/01/2008
  • 3,042 Favorites
  • Project Site
  • Comments
  • Release Type: Beta
  • License: All Rights Reserved
  • Newest File: v4.0.0-beta48
or
Support development! **
Donate

About PitBull Unit Frames 4.0

PitBull4 is a continuation of PitBull.

Differences from PitBull 3:

  • It's mostly done, but not entirely done thus why there are still only betas (despite this it is still very stable).
  • Documentation is written before functions
  • Much easier for third-party extensions.
  • Options will be much, much simpler. In 3.0, there's about 200 panels that you can mess with, it's overwhelming. I want to bring this down to somewhere around 10.
    • Layouts are defined deterministically and unit groups use the layout rather than ad-hoc layouts on a per-unit basis. This will make setting up your unit frames far, far easier.
    • Due to some decisions made, 4.0 is actually more configurable than 3.0. As a layout designer, you will have a lot more control over how things look. You can have different fonts on the same frame, different textures, more precise positioning, and a whole slough of other things.
  • CPU Efficiency will be taken much more seriously.
  • It uses Ace3 instead of Rock.

FAQ: http://www.wowace.com/addons/pitbull4.../faq/.

Guide: http://www.wowace.com/addons/pitbull4.../guide/.

If you want to help localize PitBull in your language, go to http://www.wowace.com/projects/pitbul.../localization/.

Forum thread: http://forums.wowace.com/showthread.php?t=15552...

tag v4.0.0-beta48
e12b815ec6f79b2a9b9df108a26d4a890a747002
Shefki <shefki@shefki.org>
2013-09-30 09:31:18 -0700

Tagging as v4.0.0-beta48

--------------------

Shefki:
    - This commit should fully fix the problems people have been having with SetFont() errors.  If the font returned from GetFont is nil then use our cached font and size.  Size whenever font is nil will be an uninitialized value and so the existing fix would still throw errors when the size ended up being less than or equal to 0.
    - It doesn't make sense to call GetFont on a new FontString.  The flags should not be preserved, so just set the font and size and leave the flags as "".  The AddFontString call later will set the flags properly. If the font string already exists then you want to preserve the flags.
    - Fix some typos that were fixed on nebula1169's branch.
    - Remove some values I set to help debugging ticket #1050.
    - Hopefully avoid the SetFont errors for sure now assuming that the problem is that GetFont() doesn't work immediately after a SetFont() while the game is still loading in.
    - Missed wrapping a geterrorhandler() in pcall().
    - Protect against Blizzard's error handler throwing an error, which is why the protection code didn't allow the frames to work even when the SetFont error was happening.
    - Stash the DEFAULT_FONT and DEFAULT_FONT_SIZE so I can get people having the font problem to show me what's being stored.
    - Wrap the SetFont and SetAlpha calls in pcalls() which should prevent errors with them from breaking frames entirely.
    - Make the Vengeance fix backwards compatible.
Benjamin Staneck:
    - use a different ID for vengeance that works in 5.4
Shefki:
    - Remove unnecessary constants that I added on accident.
    - Hopefully stop some rare errors in LuaTexts about SetFont.

Comments

First Previous Page 39 of 253 Next Last
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

WildStar Add-on Contest!

Enter Now!