So will there be a website set up again with a forum filled with examples of fancy slash commands and pictures of peoples unique layouts? I really miss the old site as much as flexbar ;)
Also is there going to be the GUI before slash commands are implamented? I always used the slash commands instead, but I am sure I can make do hehe.
Okay, I recently created a starter script for Flexbar2, mostly as a demonstration of how to set up the keys on a Nostromo n52 game pad, assuming that four of the keys are assigned to movement functions, while the rest are bound to particular keys. Much of this can be easily changed, and shouldn't harm anything else. This version of the script does NOT save any of the settings, so it has to be run each time you log in/reloadui. This code is intended to be placed within an in game lua capable text editor, such as Omnibus or Tinypad, etc. Edit: Omnibus has the ability to autorun code on login, not sure if any others can do this. This is how I plan to set up my buttons from now on, at least until FB2 gets a GUI and better profiles support.
Here is a screenshot of the resulting buttons:
-- First we create the button group each button will be placed in.
FlexBar2.Group:New("Nostromo1")
-- this next line is questionable. it results in placing everything where I want it,
-- but you may need to change it to suit your situation.
local uiscalerecip = (10/9)/UIParent:GetEffectiveScale()
-- spacing of 36, 8 buttons across, 3 buttons high. width is half because we're centering them.
local bWidth = (8 * 36) / 2
local bHeight = (3 * 36)
local baseX = 640*uiscalerecip-bWidth
local baseY = 768*uiscalerecip-160-bHeight
-- x is the table of x offsets from base per button.
local x = {
0, 36, 108, 144, 0, 144, 0, 36, 72, 108, 252, 216, 288, 252,
}
-- y is the table of y offsets from base per button.
local y = {
0, 0, 0, 0, 36, 36, 72, 72, 72, 72, 0, 36, 36, 72,
}
-- bind is the keys to bind each button to. note the keybinding is not permanently set,
-- so your old keybinds will still work if this script isn't run.
local bind = {
'1','2','4','5','6','R','7','A','S','D',
}
-- loop over the 14 buttons to create.
for i = 1,14 do
-- this line creates the next button to create.
FlexBar2:Generate(i)
-- set the defaults for the button.
FlexBar2.Buttons[i]:SetDefaults()
-- add the new button to the nostromo group.
FlexBar2.Group:Add("Nostromo1",FlexBar2.Buttons[i])
-- set the scale of the buttons to 90%
FlexBar2.Buttons[i]:SetScale(0.9)
-- set the position = to the base position, plus the button's offset from x and y.
FlexBar2.Buttons[i]:SetPosition(baseX+x[i],baseY+y[i])
-- Lock the position of the button.
FlexBar2.Buttons[i]:Lock()
-- show the button, otherwise it would be hidden.
FlexBar2.Buttons[i]:Show()
-- set the keybind for the button.
if bind[i] then
FlexBar2.Buttons[i]:SetBinding(bind[i])
end
end
Okay, I recently created a starter script for Flexbar2, mostly as a demonstration of how to set up the keys on a Nostromo n52 game pad, assuming that four of the keys are assigned to movement functions, while the rest are bound to particular keys. Much of this can be easily changed, and shouldn't harm anything else. This version of the script does NOT save any of the settings, so it has to be run each time you log in/reloadui. This code is intended to be placed within an in game lua capable text editor, such as Omnibus or Tinypad, etc. Edit: Omnibus has the ability to autorun code on login, not sure if any others can do this. This is how I plan to set up my buttons from now on, at least until FB2 gets a GUI and better profiles support.
Here is a screenshot of the resulting buttons:
-- First we create the button group each button will be placed in.
FlexBar2.Group:New("Nostromo1")
-- this next line is questionable. it results in placing everything where I want it,
-- but you may need to change it to suit your situation.
local uiscalerecip = (10/9)/UIParent:GetEffectiveScale()
-- spacing of 36, 8 buttons across, 3 buttons high. width is half because we're centering them.
local bWidth = (8 * 36) / 2
local bHeight = (3 * 36)
local baseX = 640*uiscalerecip-bWidth
local baseY = 768*uiscalerecip-160-bHeight
-- x is the table of x offsets from base per button.
local x = {
0, 36, 108, 144, 0, 144, 0, 36, 72, 108, 252, 216, 288, 252,
}
-- y is the table of y offsets from base per button.
local y = {
0, 0, 0, 0, 36, 36, 72, 72, 72, 72, 0, 36, 36, 72,
}
-- bind is the keys to bind each button to. note the keybinding is not permanently set,
-- so your old keybinds will still work if this script isn't run.
local bind = {
'1','2','4','5','6','R','7','A','S','D',
}
-- loop over the 14 buttons to create.
for i = 1,14 do
-- this line creates the next button to create.
FlexBar2:Generate(i)
-- set the defaults for the button.
FlexBar2.Buttons[i]:SetDefaults()
-- add the new button to the nostromo group.
FlexBar2.Group:Add("Nostromo1",FlexBar2.Buttons[i])
-- set the scale of the buttons to 90%
FlexBar2.Buttons[i]:SetScale(0.9)
-- set the position = to the base position, plus the button's offset from x and y.
FlexBar2.Buttons[i]:SetPosition(baseX+x[i],baseY+y[i])
-- Lock the position of the button.
FlexBar2.Buttons[i]:Lock()
-- show the button, otherwise it would be hidden.
FlexBar2.Buttons[i]:Show()
-- set the keybind for the button.
if bind[i] then
FlexBar2.Buttons[i]:SetBinding(bind[i])
end
end
Nice code, only one thing, SetDefaults(); is pointless if you don't do LoadSettings(); right after :)
Okay... I just uploaded the Stance Swapping code (revision 30060). There's still a little bit of work to be done, mostly to make setting the id's for swapped bars easier than is currently needed.
FlexBar2.Group:New("Nostromo1")
FlexBar2.Group.Handlers.SetStanceHeaderByClass("Nostromo1")
local uiScaleRecip = 1/UIParent:GetEffectiveScale()
local bWidth = (9 * 36) / 2
local bHeight = (3 * 36)
local baseX = uiScaleRecip * ((UIParent:GetWidth()/2)-bWidth)
local baseY = uiScaleRecip * (UIParent:GetHeight()-170-bHeight)
local x = {
0, 36, 108, 144, 0, 144, 0, 36, 72, 108, 252, 216, 288, 252,
}
local y = {
0, 0, 0, 0, 36, 36, 72, 72, 72, 72, 0, 36, 36, 72,
}
local bind = {
'1','2','4','5','6','R','7','A','S','D',
}
local TextSubs = {
[1] = "$(name)", -- or you could use $(actionid)
[2] = "$(key)",
[3] = "$(itemcount)",
[4] = "$(buttontext)",
[5] = "$(cd)",
}
for i = 1,14 do
FlexBar2:Generate(i)
local button = FlexBar2.Buttons[i]
for n, v in pairs(TextSubs) do
button:SetTextSub(n,v)
end
FlexBar2.Group:Add("Nostromo1",button)
local class = select(2,UnitClass("player"))
if class == "ROGUE" then
button:SetStanceMap("","","stealth","action", i+84)
elseif class == "WARRIOR" then
button:SetStanceMap("","","defense","action", i+84)
button:SetStanceMap("","","berserk","action", i+98)
end
-- more class based stancemaps can be added here... druids have normal, bear, cat, aquatic,
-- travel, moonkin, and stealth (for prowl) at the moment. Druid stuff is untested atm.
button:SetStanceMap("","","normal","action", i)
-- the arguments to pass to SetStanceMap are:
-- ("","",stance,"action",actionid)
-- at least at the moment, not much else will work with SetStanceMap.
-- if you're not using stances, you can use:
-- button:SetNormalMap("","","action",i)
-- and you can replace "action" and i with say, "spell", "Rejuvenate",
-- or "macro", "/cast Rejuvenate"
button:SetScale(0.9)
button:SetPosition(baseX+x[i],baseY+y[i])
button:Lock()
button:Show()
button:SetBinding(bind[i])
end
I've always loved Flesbar, and now that it seems like I will be able to use it once again, I'm very excited. One thing I do want to see is the ability to skin buttons with CyCircle or in some fashion. Although this may be more of a request for that addon and not this.
Okay, I just uploaded revision 30083, which fixes some of the weird right click and left click errors Ominous reported to me in IRC. It also fixes Keybinds so they show up correctly, regardless of whether you save variables or whether you use a script to configure (like my code above).
I've always loved Flesbar, and now that it seems like I will be able to use it once again, I'm very excited. One thing I do want to see is the ability to skin buttons with CyCircle or in some fashion. Although this may be more of a request for that addon and not this.
The way Flexbar currently works skinning could be done quite easely
Can we get slash commands before any kind of GUI configuration? I used to only use the slash commands for flexbar1 and would like to use them for flexbar2 too
That is kind of how I feel, I would rather have easy to use slash commands than a GUI. Having a visual way of setting up your bars can be nice, but it also seems like you are limited in what you can do.
Waiting for a GUI just seems like a waste to me, if it is much easier for both the programmer to create and many users to just use slash commands. It would take some time to type up a readme file for examples of how to use the commands though, with a list of what each function does.
That is kind of how I feel, I would rather have easy to use slash commands than a GUI. Having a visual way of setting up your bars can be nice, but it also seems like you are limited in what you can do.
Waiting for a GUI just seems like a waste to me, if it is much easier for both the programmer to create and many users to just use slash commands. It would take some time to type up a readme file for examples of how to use the commands though, with a list of what each function does.
Slash commands and GUI are likely to be developed at the same time, with precedence on slash commands.
I expect to be able to start on that stuff in a few days. I want to get stances, actionbars, and stealth all working perfectly with each other, and fully configurable first.
EDIT: I can see the information I'm looking for in the ButtonMapping area. Incredible! I'll get on putting some scripts together. Is there a place where we can post examples or layouts for others who want to use FlexBar?
--
I have been using FlexBar since the beginning... until 2.0 came along and broke it.
I found, playing a druid, that FlexBar was almost a necessity because of the ability to remap on stance or form change.
Is this functionality still in there? I have been following the code changes for a while, but I didn't know how far it had really come until I heard of people using slash commands. I relied on my personalized configuration of FlexBar extensively and I want to be able to use that same functionality again.
I appreciate you guys picking up the torch again and running with it... I'd love a leg up, though, on what some of the commands are. I see that "/scripts" is the way to initiate FlexBar now. Is there anything else that I should know to get back into it?
I just wanted to poke my head in here to get some information from you guys.
I was using FlexBar1 for AGES before 2.0, like most of us here. I did stance swapping on my warrior and rogue by making a group for each stance and then just show/hiding them depending on state. It was messy and unless I entered the events in a certain order FlexBar would lock the client for about 10 sec rashing on the commands. In some situations if I was mind controlled by an npc and had no stance on my warrior no bar would show up till I went into a stance (Nef tanking with no defensive stance bar from being pollied by a mage lol).
Currently I have been using Bartender3 and have to say I really like it. Easy to configure and setup. The way Bartender3 does bar swapping is nice too since I can setup a bar for each of two stances, have them swap to a third and just have the third stance be the normal buttons on the bar. From what I can see in FlexBar2 I can do either of these methods.In Bartender3 I have been using the Zoomed button style and have grown very accustomed to it, so please include button skinning abilities. Would love if you could include some button skins at release but you know release alone is good too.
I am one of those people who will favor using a GUI for setup and am also one of those people who would like to make things look pretty. The command line commands grew pretty nasty and I remember more than a few times having to enter a command string more than once due to misspellings or improper ordering.
Looks like Flex will once again be my bar mod (no surprise) and I thank all the devs for their hard work. /salute /cheer
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
They are already customizable, but there ain't a way to change it yet except through directly changes the vars :)
Awesome.. colored buttons!
But I meant via the FB2 GUI ;) or old-style / commands. ^_^
Regards
those will come eventualy
Also is there going to be the GUI before slash commands are implamented? I always used the slash commands instead, but I am sure I can make do hehe.
/flex for a bump disguised as a valid post
Here is a screenshot of the resulting buttons:
-- First we create the button group each button will be placed in. FlexBar2.Group:New("Nostromo1") -- this next line is questionable. it results in placing everything where I want it, -- but you may need to change it to suit your situation. local uiscalerecip = (10/9)/UIParent:GetEffectiveScale() -- spacing of 36, 8 buttons across, 3 buttons high. width is half because we're centering them. local bWidth = (8 * 36) / 2 local bHeight = (3 * 36) local baseX = 640*uiscalerecip-bWidth local baseY = 768*uiscalerecip-160-bHeight -- x is the table of x offsets from base per button. local x = { 0, 36, 108, 144, 0, 144, 0, 36, 72, 108, 252, 216, 288, 252, } -- y is the table of y offsets from base per button. local y = { 0, 0, 0, 0, 36, 36, 72, 72, 72, 72, 0, 36, 36, 72, } -- bind is the keys to bind each button to. note the keybinding is not permanently set, -- so your old keybinds will still work if this script isn't run. local bind = { '1','2','4','5','6','R','7','A','S','D', } -- loop over the 14 buttons to create. for i = 1,14 do -- this line creates the next button to create. FlexBar2:Generate(i) -- set the defaults for the button. FlexBar2.Buttons[i]:SetDefaults() -- add the new button to the nostromo group. FlexBar2.Group:Add("Nostromo1",FlexBar2.Buttons[i]) -- set the scale of the buttons to 90% FlexBar2.Buttons[i]:SetScale(0.9) -- set the position = to the base position, plus the button's offset from x and y. FlexBar2.Buttons[i]:SetPosition(baseX+x[i],baseY+y[i]) -- Lock the position of the button. FlexBar2.Buttons[i]:Lock() -- show the button, otherwise it would be hidden. FlexBar2.Buttons[i]:Show() -- set the keybind for the button. if bind[i] then FlexBar2.Buttons[i]:SetBinding(bind[i]) end endNice code, only one thing, SetDefaults(); is pointless if you don't do LoadSettings(); right after :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThanks for your work, I used Flexbar when I first started playing WoW. This is looking promising.
I've been working on stances, etc. for rogue stealth, warrior stances, and druid shapeshift forms.
The code to handle what you're asking for is a bit more complex... but it is on the way for FlexBar2. Eventually I'll figure it out. :)
Once I get enough of the system set up, I'll be working on integrating a GUI.
FlexBar2.Group:New("Nostromo1") FlexBar2.Group.Handlers.SetStanceHeaderByClass("Nostromo1") local uiScaleRecip = 1/UIParent:GetEffectiveScale() local bWidth = (9 * 36) / 2 local bHeight = (3 * 36) local baseX = uiScaleRecip * ((UIParent:GetWidth()/2)-bWidth) local baseY = uiScaleRecip * (UIParent:GetHeight()-170-bHeight) local x = { 0, 36, 108, 144, 0, 144, 0, 36, 72, 108, 252, 216, 288, 252, } local y = { 0, 0, 0, 0, 36, 36, 72, 72, 72, 72, 0, 36, 36, 72, } local bind = { '1','2','4','5','6','R','7','A','S','D', } local TextSubs = { [1] = "$(name)", -- or you could use $(actionid) [2] = "$(key)", [3] = "$(itemcount)", [4] = "$(buttontext)", [5] = "$(cd)", } for i = 1,14 do FlexBar2:Generate(i) local button = FlexBar2.Buttons[i] for n, v in pairs(TextSubs) do button:SetTextSub(n,v) end FlexBar2.Group:Add("Nostromo1",button) local class = select(2,UnitClass("player")) if class == "ROGUE" then button:SetStanceMap("","","stealth","action", i+84) elseif class == "WARRIOR" then button:SetStanceMap("","","defense","action", i+84) button:SetStanceMap("","","berserk","action", i+98) end -- more class based stancemaps can be added here... druids have normal, bear, cat, aquatic, -- travel, moonkin, and stealth (for prowl) at the moment. Druid stuff is untested atm. button:SetStanceMap("","","normal","action", i) -- the arguments to pass to SetStanceMap are: -- ("","",stance,"action",actionid) -- at least at the moment, not much else will work with SetStanceMap. -- if you're not using stances, you can use: -- button:SetNormalMap("","","action",i) -- and you can replace "action" and i with say, "spell", "Rejuvenate", -- or "macro", "/cast Rejuvenate" button:SetScale(0.9) button:SetPosition(baseX+x[i],baseY+y[i]) button:Lock() button:Show() button:SetBinding(bind[i]) endThe way Flexbar currently works skinning could be done quite easely
Waiting for a GUI just seems like a waste to me, if it is much easier for both the programmer to create and many users to just use slash commands. It would take some time to type up a readme file for examples of how to use the commands though, with a list of what each function does.
Slash commands and GUI are likely to be developed at the same time, with precedence on slash commands.
I expect to be able to start on that stuff in a few days. I want to get stances, actionbars, and stealth all working perfectly with each other, and fully configurable first.
Im going nuts looking at blizz standart ui ^^
Must have flexbar again =)
CNC you're really doing a great job, and cant really thank you enough for putting the mod together gain =)
//CR
--
I have been using FlexBar since the beginning... until 2.0 came along and broke it.
I found, playing a druid, that FlexBar was almost a necessity because of the ability to remap on stance or form change.
Is this functionality still in there? I have been following the code changes for a while, but I didn't know how far it had really come until I heard of people using slash commands. I relied on my personalized configuration of FlexBar extensively and I want to be able to use that same functionality again.
I appreciate you guys picking up the torch again and running with it... I'd love a leg up, though, on what some of the commands are. I see that "/scripts" is the way to initiate FlexBar now. Is there anything else that I should know to get back into it?
Thanks in advance!
I was using FlexBar1 for AGES before 2.0, like most of us here. I did stance swapping on my warrior and rogue by making a group for each stance and then just show/hiding them depending on state. It was messy and unless I entered the events in a certain order FlexBar would lock the client for about 10 sec rashing on the commands. In some situations if I was mind controlled by an npc and had no stance on my warrior no bar would show up till I went into a stance (Nef tanking with no defensive stance bar from being pollied by a mage lol).
Currently I have been using Bartender3 and have to say I really like it. Easy to configure and setup. The way Bartender3 does bar swapping is nice too since I can setup a bar for each of two stances, have them swap to a third and just have the third stance be the normal buttons on the bar. From what I can see in FlexBar2 I can do either of these methods.In Bartender3 I have been using the Zoomed button style and have grown very accustomed to it, so please include button skinning abilities. Would love if you could include some button skins at release but you know release alone is good too.
I am one of those people who will favor using a GUI for setup and am also one of those people who would like to make things look pretty. The command line commands grew pretty nasty and I remember more than a few times having to enter a command string more than once due to misspellings or improper ordering.
Looks like Flex will once again be my bar mod (no surprise) and I thank all the devs for their hard work. /salute /cheer