Tlhough not anything similar to a bar by any means, I replaced AutoBar with OPie. No fluff like LunarSpheres. It has only what you tell it to, and isn't even visible until you tell it to be - and then it only shows what you tell it to :)
Opie's a good one. My problem is that it eats up a keybinding. I use Opie for a few things I need quickly.. hunter aspects, traps. Other stuff... I don't mind having a button on my screen, and then a fly-out menu of buttons, ala Autobar...
Ah well, might be time to use my Function keys for more, lesser-used Opie wheels.
Are the items that needs to be hard coded still being updated? Even with flasks, potions, etc I noticed Autobar missing a bunch that were in my inventory. What are people doing to work around this?
Mostly. PeriodicTable still gets updated and refreshes are posted based on that. At the moment the wowhead miner seems broken for some things though so it may be a while till a refresh.
just downloaded and installed new update and having a problem with the fishing and non combat pets in extras bar it wont bring up the tooltip or let me use either one of those buttons.
Recent versions of LibButtonFacade create a new anonymous texture for each border layer since SetVertexColor() is so horribly implemented. The relevant code will first check for the border color passed in the "Color" argument of the Skin() method. If not present, it will use the old border object's vertex color.
Two issues arise for AutoBar because of the way the buttons themselves load. The first is that the Color argument isn't passed on load, preventing the appropriate border colors to be applied initially. However, if a user adjusts the skin, etc, the colors get applied. The second is that since the border textures seem to load late, LBF is unable to get the correct vertex color of the original border texture object (The color is set later on).
There's a few solutions. The first would to be ensure that any button updates receive a new :Skin() call. The second, and simplest, would be to explicitly set the border color through the LBF method :SetBorderColor().
Feel free to look through LBF's code. Hell, I may have missed something, but I'd like users to be able to have their AutoBar look right. :)
4/10/10 release does not reorder mounts according to use. Instead, it selects type of mount depending upon type of mount permitted in the current zone. This cannot be changed by selecting the option again, instead it throws a lua error
I have been trying to create a new bar/button/catagory using this addon. I am making a bar with 2 buttons (one for mounts one for pets) each one will have a static keybound button for a specific mount or pet but a flyout menu of the pets and mounts I want easy quick access to. I understand how to do this but the problem I am having is being unable to add pet or mount, or any spells to the catagory. This is what I see which according to your webpage is not what I should be seeing.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Opie's a good one. My problem is that it eats up a keybinding. I use Opie for a few things I need quickly.. hunter aspects, traps. Other stuff... I don't mind having a button on my screen, and then a fly-out menu of buttons, ala Autobar...
Ah well, might be time to use my Function keys for more, lesser-used Opie wheels.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI've found myself having to drag Corroded Skeleton Key onto my action bars so I can hit it with a keybind.
Many items need to be hard coded. I suspect this is one of them.
Mmm this was mined a while back. I tagged a new version though so the latest should include it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumReleases like that are to pick up PeriodicTable changes.
This works for me. Note that pets take a while to show sometimes as it is dependent on blizzard downloading the info.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's working just fine for me. What exactly is broken?
If not that could be the reason (US servers have the new patch, the rest of the servers will get it next week)
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTwo issues arise for AutoBar because of the way the buttons themselves load. The first is that the Color argument isn't passed on load, preventing the appropriate border colors to be applied initially. However, if a user adjusts the skin, etc, the colors get applied. The second is that since the border textures seem to load late, LBF is unable to get the correct vertex color of the original border texture object (The color is set later on).
There's a few solutions. The first would to be ensure that any button updates receive a new :Skin() call. The second, and simplest, would be to explicitly set the border color through the LBF method :SetBorderColor().
Feel free to look through LBF's code. Hell, I may have missed something, but I'd like users to be able to have their AutoBar look right. :)
Error: wrapped ~= preBody in UnwrapScript
AddOn: AutoBar
File: AutoBarButton.lua
Line: 339
Count: 1
Is there any way to enable a range check on the autobar bars?? And if so, how?
Thanks in advance :)