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.
I seemed to have the same issue with bindings and oddly enough, fadeouts.
Here's my steps to fix however:
With the /dom options OPEN, bindings mode doesn't work, and upon hovering over a bar with 0 fadeout opacity and 100 regular opacity, I cannot see them still.
However, if I /dom -> enter binding mode -> close options dialog
I can now keybind normally. Then I just /dom and exit binding mode, and it works fine. I still can't see my fadeouts while I'm in keybinding mode, but hey, they work when it's closed, so it's workable.
edit: I too had bongos3 and dominos enabled 1 login because like a tool I forgot to disable Bongos. Maybe this is what is causing the issue?
Planning to switch to this soon now that its on WoWI. One question though, does no "true variable length bars" mean that I can't have an 8 button bar, or does it just mean I can't have a bar with more than 12 buttons?
Planning to switch to this soon now that its on WoWI. One question though, does no "true variable length bars" mean that I can't have an 8 button bar, or does it just mean I can't have a bar with more than 12 buttons?
As far as I understand it, you can shorten a bar but you only get 10 bars of 12 buttons each.
You can also set how many action bars you have total via /run Dominos:SetNumBars(number)
I'll fix bugs with it, but will likely not support it directly (this may change if I feel like it).
I'm not likely to add a one bag setting to the bag bar. At that point, I'd feel you should be pressing "B" :P
Dominos 1.1.1 is up
* Fixed a bug with the roll frame layout code
* Fixed a bug causing right clicking a frame in config mode to run the sticky logic
* The interface options menu will now hide when entering binding mode.
* Made the buff highlighting code more generic. It'll work on any standard action button that is loaded after it. (That means, "Hey nev, get off your ass and make bartender4 use the stock action buttons")
I still find the one bag setting helpful for when I'm typing in chat but also need to open my bags. It's also nice because I have it display the number of empty slots in my bag. Neither is really important though and something I can def live with out, just used to it is all. Would like to see one bag implemented into Dominos, but if not, no biggie.
You can also set how many action bars you have total via /run Dominos:SetNumBars(number)
I'll fix bugs with it, but will likely not support it directly (this may change if I feel like it).
It works fine right now but like I said earlier, it would make a whole lot more sense if you flipped it around to SetMaxButtonsPerBar(number).
I can't really say I am missing anything, the range thing - pfft I'll use RedRange :P Bags are ok, I never did use the other parts in Bongos other then the stats module, which I've now written for myself (just basic stuff in a MoonUI addon combined with some panelling and all that). So I think you've done it :P
Dominos 1.1.0 is up
* Adjusted defaults to have better spacing and padding settings for action bars
* Dominos now uses the same skin as Bongos if button facade is not installed
* Fixed a bug with action buttons not loading events after changing profiles and not reloading your interface
I'm calling this version stable. I'll be writing up a more detailed guide and sticking it on wowi shortly.
You did something here, my ButtonFacade isn't working decently. I changed skins and now no skin will apply as it should. Could you look into it? It happened between this version and 2 versions ago >.< To be more precise, which might help :P, the sizes etc apply properly, the textures however don't show up anymore.
Tooltip hiding:
This is one I've had to think about. On one hand, its one of those things I don't use. On the other hand, I'm already hooking the onenter functions to get kb working. So I've decided to implement this functionality.
i am very happy with dominos.. ok.. i was happy with bongos3 and bt4 too.
but i don't need any other features.. i don't even use all the plugins
the cpu & mem usage is really low!
This is such a typical user view these days it makes me god damn cry because you have NO IDEA what you're talking about. Here's an FYI.
Bar addons
Choice #1, reuse blizzard code, have all the cpu and memory usage blamed on blizzard
Choice #2, create everything yourself, use your own onupdates, and have all mem and cpu blamed on your addon.
You think 1 is better? Wrong, in most cases #2 is better, because blizzard coding can be really shitty. I'd rather use my own better coded onupdate than blizzards with a bunch of useless stuff, but that would make my mod shit because it would get blamed for all the cpu usage................
Can users PLEASE go back to using addons for features, ARG.
Here's my steps to fix however:
With the /dom options OPEN, bindings mode doesn't work, and upon hovering over a bar with 0 fadeout opacity and 100 regular opacity, I cannot see them still.
However, if I /dom -> enter binding mode -> close options dialog
I can now keybind normally. Then I just /dom and exit binding mode, and it works fine. I still can't see my fadeouts while I'm in keybinding mode, but hey, they work when it's closed, so it's workable.
edit: I too had bongos3 and dominos enabled 1 login because like a tool I forgot to disable Bongos. Maybe this is what is causing the issue?
Though the only thing I need to make the switch from Bongos is to be able to condense the bag bar/keyring into one button.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumShift-right-click or click the middle mouse button to make a bar invis.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAs far as I understand it, you can shorten a bar but you only get 10 bars of 12 buttons each.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'll fix bugs with it, but will likely not support it directly (this may change if I feel like it).
I'm not likely to add a one bag setting to the bag bar. At that point, I'd feel you should be pressing "B" :P
Dominos 1.1.1 is up
* Fixed a bug with the roll frame layout code
* Fixed a bug causing right clicking a frame in config mode to run the sticky logic
* The interface options menu will now hide when entering binding mode.
* Made the buff highlighting code more generic. It'll work on any standard action button that is loaded after it. (That means, "Hey nev, get off your ass and make bartender4 use the stock action buttons")
It works fine right now but like I said earlier, it would make a whole lot more sense if you flipped it around to SetMaxButtonsPerBar(number).
And thanks also for the note on hiding bars.
Dominos has replaced Bongos- what a great mod!
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorYou did something here, my ButtonFacade isn't working decently. I changed skins and now no skin will apply as it should. Could you look into it? It happened between this version and 2 versions ago >.< To be more precise, which might help :P, the sizes etc apply properly, the textures however don't show up anymore.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTooltip hiding:
This is one I've had to think about. On one hand, its one of those things I don't use. On the other hand, I'm already hooking the onenter functions to get kb working. So I've decided to implement this functionality.
but i don't need any other features.. i don't even use all the plugins
the cpu & mem usage is really low!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDominos 1.2.0 is up
* Renamed any buttons that were still named Mangos
* Added an option to hide button tooltips
Ok, I'll redo Saved Variables. :)
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThis is such a typical user view these days it makes me god damn cry because you have NO IDEA what you're talking about. Here's an FYI.
Bar addons
Choice #1, reuse blizzard code, have all the cpu and memory usage blamed on blizzard
Choice #2, create everything yourself, use your own onupdates, and have all mem and cpu blamed on your addon.
You think 1 is better? Wrong, in most cases #2 is better, because blizzard coding can be really shitty. I'd rather use my own better coded onupdate than blizzards with a bunch of useless stuff, but that would make my mod shit because it would get blamed for all the cpu usage................
Can users PLEASE go back to using addons for features, ARG.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium