Blizzard designed their interface around the 12 buttons design, so things tend to work well if you stick to the old 10 bars of 12 buttons each thing. That's the big reason that the /dom numbars and numbuttons commands are slash only, as well as a major reason why I discontinued Bongos3. Its also the reason Bartender4 makes no attempt at supporting variable bar layouts.
I think I can solve your specific problem via making a Dominos_Possess addon, (aka a separate possess bar), but am debating if I should do so or not.
Is it possible to overlap each button of what Blizz wants to possess to each button of Dominos? For instance: Possess Button 3 is Dominos Button/Bar 3.
1.8.0 is out. The major change in this version is that I've introduced a new layer that allows Dominos to seamlessly interact with both the stock blizzard and click bindings.
I'm still deciding what to do about the possess bar, and if I want to add in a separate option or not. I have a few options:
Make the pet bar the possess bar. The pro here is that I'll be able to reuse the pet bar bindings. The con, and its a big one, is that I'm going to have to make my own pet bar instead of reusing the Blizzard one. That goes against my goal of making Dominos reuse as much code from the stock interface as possible.
Make a separate possess bar. The pro: I get to implement those nifty extra possess buttons. The con: The need for separate bindings.
Completely ignore this issue. I don't want to do this, since I still sort of want to support people with a variable number of bars.
Also, I have a todo list of sorts here: here. If there's anything I'm missing that I've said I'd look into, please tell me. Crazy town == probably won't do. Super crazy town extreme edition == almost definitely won't do.
A secure modal layout system means:
* [form:1] -> Dominos layout;
* [modifier:alt] -> another layout;
* [group] -> yet another layout
Its the secure header stuff taken to the complete (and probably still impossible) extreme. I'll probably research it at some point in the future, but that would be yet another bar addon :P
I'd vote for option 1 as an optional module, with option 3 for those that don't want option 1. I honestly don't know where I'd make room in my UI for another bar that's situational and rarely used.
Was it just the Zombie possess that wasn't working correctly? Steam tonks were working with the pet bar before you took it out, but I can't confirm that things like Chess Event, Teron, or KJ were.
I've done the Chess event a few times recently, and everything works as expected with the Possess bar set to Bar 1. Had a similarly flawless experience with Teron Gorefiend. As long as the current Possess bar functionality is preserved, I don't mind how fancy you make it for others.
RE: Dominos roadmap
- I'm personally not that fussed with changing the 12-buttons per bar layout. But many people do like it.
- Built-in RedRange? Yes, please. :)
- I thought Dominos was basically just the stuff you thought you'd personally use. Seems to be an awful lot of exotic features creeping in here. :P
RE: Bagnon Forever
- Guild Bank support, go go!
RE: Sage
- I know of at least one person who will love you forever if you get this updated for Wrath. It's impossible to find a working substitute. So hard to find simple, clean unitframes with very clear debuff highlighting.
The battle of me as a designer is what I actually need versus what I think would be interesting to have. Bongos3 swung me in the "interesting to implement direction" and Dominos swung back. Either way "crazy town" features are things I don't expect to implement.
As far as what I do next, its either Bagnon or Sage. Dominos has a high chance of staying at 1.8.x for a good while, but might hit 1.9.x if I make a possess bar decision.
I vote for Sage before Bagnon... make people use Combuctor :P
As for the possess bar, correct me if I'm wrong but it is ONLY an issue for those that make bars shorter than X buttons (x being the number needed for the possessed functions). Since you're still reusing Blizzards buttons/bars it seems to me that one approach (that I'm not sure how to do in an elegant way) would be to allow multiple dominos bars to be combine for the possess bar with a simple ordered overflow. For the possess bar you'd specify either:
1) The first bar to be used and have dominos automatically overflow into the next bar.
2) Assign a priority order of bars to be used for the possess bar with Dominos using as many as needed.
Lets say that you use 1 button bars like a previous poster does. If he specifies that bar 4 would be his possess bar and we're using option 1, a 4 button possess bar would be using bar 4,5,6 and 7.
This is purely a cosmetic enhancement, but I'd like to have my bars faded out completely all of the time, except on mouse-over. But I'd like the bars to ignore their faded setting whenever I'm in combat. Is there a way to do this that I'm missing?
Using v1.9.0 on live, I get no primary action bar if I log in or reloadui while in a Druid shapeshift form. I have to shift out and reload my UI to get it back. This also happened in 1.8.3.
I've noticed that recently the text showing what keys are mapped to various buttons (such as 1-9.0.-.= for the main action bar) has been shifted to the right so that it almost appears to be on the next button to the right of where it should be. This has been causing me confusion. I can try to post a screenshot later if noone else is seeing this.
Anyone else notice that sometimes Dominos will forget that you want to keep the experience bar text-free? I can't figure out the exact circumstances, but I often need to turn the options on and then off again.
I am trying to build a custom interface using kgpanels to hide aspects, however I can not find out the frame name that dominos uses or anyone was to toggle action bars for dominos by command line (/script is technically what kgpanels uses for onclick).
Dominos frames are nameless. Dominos.Frame:Get(id) (ex Dominos.Frame:Get("pet") or Dominos.Frame:Get(1) is the code to retrieve a Dominos frame, though.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIs it possible to overlap each button of what Blizz wants to possess to each button of Dominos? For instance: Possess Button 3 is Dominos Button/Bar 3.
Or is that what you are talking about?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'm still deciding what to do about the possess bar, and if I want to add in a separate option or not. I have a few options:
Also, I have a todo list of sorts here: here. If there's anything I'm missing that I've said I'd look into, please tell me. Crazy town == probably won't do. Super crazy town extreme edition == almost definitely won't do.
A secure modal layout system means:
* [form:1] -> Dominos layout;
* [modifier:alt] -> another layout;
* [group] -> yet another layout
Its the secure header stuff taken to the complete (and probably still impossible) extreme. I'll probably research it at some point in the future, but that would be yet another bar addon :P
Was it just the Zombie possess that wasn't working correctly? Steam tonks were working with the pet bar before you took it out, but I can't confirm that things like Chess Event, Teron, or KJ were.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRE: Dominos roadmap
- I'm personally not that fussed with changing the 12-buttons per bar layout. But many people do like it.
- Built-in RedRange? Yes, please. :)
- I thought Dominos was basically just the stuff you thought you'd personally use. Seems to be an awful lot of exotic features creeping in here. :P
RE: Bagnon Forever
- Guild Bank support, go go!
RE: Sage
- I know of at least one person who will love you forever if you get this updated for Wrath. It's impossible to find a working substitute. So hard to find simple, clean unitframes with very clear debuff highlighting.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAs far as what I do next, its either Bagnon or Sage. Dominos has a high chance of staying at 1.8.x for a good while, but might hit 1.9.x if I make a possess bar decision.
As for the possess bar, correct me if I'm wrong but it is ONLY an issue for those that make bars shorter than X buttons (x being the number needed for the possessed functions). Since you're still reusing Blizzards buttons/bars it seems to me that one approach (that I'm not sure how to do in an elegant way) would be to allow multiple dominos bars to be combine for the possess bar with a simple ordered overflow. For the possess bar you'd specify either:
1) The first bar to be used and have dominos automatically overflow into the next bar.
2) Assign a priority order of bars to be used for the possess bar with Dominos using as many as needed.
Lets say that you use 1 button bars like a previous poster does. If he specifies that bar 4 would be his possess bar and we're using option 1, a 4 button possess bar would be using bar 4,5,6 and 7.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumEdit: Will respond to the ticket (yeah that's me :))
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAny help would be aprpeciated
-
View User Profile
-
View Posts
-
Send Message
Curse Premium