ok. It's time to get serious. Could someone give me a starting point ACEConfig code snip that would be a multiline scrolling non-editable text box. The lines would already be populated and when I select a line it will highlight. :)
Torhal: If AceGUI is misnamed, then what should the lib be used for?
Maybe AceConfig is what I should be using. Here is what I am trying to do. Years ago there was an addon, automessanger that you could type a string in an editbox, and set which channel to repeat the message with a interval of 20 seconds to 3 minutes. What I'd like to do is type /automsg, a panel comes up and has a multiline history and an textedit box. If i select a line in the history box, it copies to the testedit box, I then have a slider for the time to repeat and a start and stop button. So, for example "LFG for Crucible" or "LF2M for Crucible". If I type something new in the editbox it will save to history when I press start. Also, there will be a delete history line button.
ok, this is not a config panel. this is a panel to interact with to accomplish something. Like panda lets say. I take it you would not recommend AceConfig in this case? Also, another question. Is there a small addon out there that I can learn from? I'm getting kind of lost with the bigger addons...
sry the acegui. the example shows:
f:SetCallback("OnClose",function(widget) AceGUI:Release(widget) end)
here is the example.
local AceGUI = LibStub("AceGUI-3.0")
-- Create a container frame
local f = AceGUI:Create("Frame")
f:SetCallback("OnClose",function(widget) AceGUI:Release(widget) end)
f:SetTitle("AceGUI-3.0 Example")
f:SetStatusText("Status Bar")
f:SetLayout("Flow")
-- Create a button
local btn = AceGUI:Create("Button")
btn:SetWidth(170)
btn:SetText("Button !")
btn:SetCallback("OnClick", function() print("Click!") end)
-- Add the button to the container
f:AddChild(btn)
Don't recreate every time. Do not do that. Ever. Frames are not released or recycled or reclaimed in anyway. Constantly recreating a GUI is a huge waste of memory.
Create it once, either during addon initialization or on demand the first time the user needs it.
ok, so I would not use the release api then, correct? just hide and show
edit: maybe it just me but I thought the toon in question didn't have the arrow on the tab. That made it harder to figure out it is a button. I'll check. The toon i'm on now has the arrow on the tab.
I guess my question is a little more complex. I followed the getting started but also had a form in core.xml instead of writing the code out in core.lua. When I do that, I get the error. I'm using addon Studio to design the form but I'm now wondering if that's compatible with ace3. Put another way, I'm I just going to have trouble if I design a form in the .xml file if I use ace3?
If I use ace3, Is it not advisable to do the frame coding in let's say core.xml and instead code it out in core.lua? I'm trying both and getting a null on libstub, which I guess means the core.xml is being called before it's ready.
If I use ace3, Is it not advisable to do the frame coding in let's say core.xml and instead code it out in core.lua? I'm trying both and getting a null on libstub, which I guess means the core.xml is being called before it's ready.
But there's nothing that comes close to the features I want. The features that cart provided. I think if there aren't massive changes to librock, it would be worth it to get that piece working until (and if) someone comes up with a map replacement we all can live with.
ok. question for you. I'm not a full time coder by any means. Because it's a function in a function it's no longer callable because it's not global. Is that correct?
0
0
Maybe AceConfig is what I should be using. Here is what I am trying to do. Years ago there was an addon, automessanger that you could type a string in an editbox, and set which channel to repeat the message with a interval of 20 seconds to 3 minutes. What I'd like to do is type /automsg, a panel comes up and has a multiline history and an textedit box. If i select a line in the history box, it copies to the testedit box, I then have a slider for the time to repeat and a start and stop button. So, for example "LFG for Crucible" or "LF2M for Crucible". If I type something new in the editbox it will save to history when I press start. Also, there will be a delete history line button.
0
0
f:SetCallback("OnClose",function(widget) AceGUI:Release(widget) end)
here is the example.
local AceGUI = LibStub("AceGUI-3.0")
-- Create a container frame
local f = AceGUI:Create("Frame")
f:SetCallback("OnClose",function(widget) AceGUI:Release(widget) end)
f:SetTitle("AceGUI-3.0 Example")
f:SetStatusText("Status Bar")
f:SetLayout("Flow")
-- Create a button
local btn = AceGUI:Create("Button")
btn:SetWidth(170)
btn:SetText("Button !")
btn:SetCallback("OnClick", function() print("Click!") end)
-- Add the button to the container
f:AddChild(btn)
0
ok, so I would not use the release api then, correct? just hide and show
0
What would be the best way?
User types in a / command, I create and show a dialog panel, then user closes. The user might do this a few times.
Do I: create the panel and then hide it on close, then do a show when they go back in?
or with local variables in functions would I create from scratch and then release each time?
etc...
0
edit: maybe it just me but I thought the toon in question didn't have the arrow on the tab. That made it harder to figure out it is a button. I'll check. The toon i'm on now has the arrow on the tab.
0
0
0
p.s. go easy on me, i'm not a full time coder
I had this question in the wrong forum b4
0
p.s. go easy on me, i'm not a full time coder
0
But there's nothing that comes close to the features I want. The features that cart provided. I think if there aren't massive changes to librock, it would be worth it to get that piece working until (and if) someone comes up with a map replacement we all can live with.
0
12/12 08:15:35.640 An action was blocked in combat because of taint from Cartographer_LookNFeel - WorldMapDetailFrame:SetParent()
12/12 08:15:35.640 Interface\AddOns\Cartographer_LookNFeel\LookNFeel.lua:570 refixParent()
12/12 08:15:35.640 Interface\AddOns\Cartographer_LookNFeel\LookNFeel.lua:1157 SetAlpha()
12/12 08:15:35.640 Interface\AddOns\Cartographer_LookNFeel\LookNFeel.lua:1144
12/12 08:15:35.640 pcall()
12/12 08:15:35.640 Interface\AddOns\FuBar\libs\LibRockEvent-1.0\LibRockEvent-1.0.lua:469
12/12 08:15:35.640 Interface\AddOns\Cartographer\Cartographer.lua:1035
12/12 08:15:35.640 pcall()
12/12 08:15:35.640 Interface\AddOns\FuBar\libs\LibRockEvent-1.0\LibRockEvent-1.0.lua:469
0
0
oh, and thanks.