Re: Löve Frames - A GUI Library
Posted: Wed May 13, 2015 6:25 pm
So I've been toying with Loveframes and seem to be running into some confusion. Actually, it isn't exactly a Loveframes issue, but probably more so my newbie experience with lua code structure and proper use of modules. I think lua threw out some error about a loop when I try to require my modules. Shrug. To avoid a rather long post, I'll simply start with this:
Suppose I have a single button placed in the top right corner. When you click on it a function (via OnClick) then creates a panel populated with 8 buttons. The very last button is labeled "Exit" and its 'Onclick' function does nothing more then turn the panel invisible. So what happens when I do this again, or 5 times, or a hundred times? Does Loveframes keep making new objects or does it keep just what it needs? Would it be better to create the objects (The first button, the panel, and the panel objects) with some sort of init function in love.load? Or does it even matter?
If it doesn't matter and there are no hidden 'gotchas' I've yet to notice, I think I might be able to reduce or eliminate some module dependencies. Hopefully this post made some sense, but I doubt it. Any suggestions or comments appreciated.
One other thing is this. In the documentation on skinning it is stated:
That last line doesn't seem to be true or I've missed something. I've created my own skin and it works just fine, but I only created that skin for use with only certain panels and buttons. The skin has a custom draw function for the panel object and different images for the button object. Everything else still uses the default 'Blue' skin. So when I do this:
The panel gets drawn differently as expected, but the buttons still have the default skin attached. The only way I can get the buttons to show up with the new skin values is to add SetSkin("WWar") to each button. Aren't the buttons the children of the panel? Have I missed something here?
Suppose I have a single button placed in the top right corner. When you click on it a function (via OnClick) then creates a panel populated with 8 buttons. The very last button is labeled "Exit" and its 'Onclick' function does nothing more then turn the panel invisible. So what happens when I do this again, or 5 times, or a hundred times? Does Loveframes keep making new objects or does it keep just what it needs? Would it be better to create the objects (The first button, the panel, and the panel objects) with some sort of init function in love.load? Or does it even matter?
If it doesn't matter and there are no hidden 'gotchas' I've yet to notice, I think I might be able to reduce or eliminate some module dependencies. Hopefully this post made some sense, but I doubt it. Any suggestions or comments appreciated.
One other thing is this. In the documentation on skinning it is stated:
Code: Select all
loveframe.util.SetActiveSkin("SKINNAME")
Doing this will change the active skin. If you only want to change the skin of one object you can do so like this:
local panel = loveframes.Create("panel")
panel:SetSkin("SKINNAME")
**Doing this will change the object's skin to the skin specified. It will also change all of the object's children's skins recursively.**Code: Select all
local panel = loveframes.Create("panel")
panel:SetSkin("WWar"):SetSize(500, 500):SetPos(512, 384, true)
local button = loveframes.Create("button", panel)
button:SetSize(32,14):SetText("Testing"):CenterX():SetY(32)
button.OnClick = function() end
local button2 = loveframes.Create("button", panel)
button2:SetSize(32,14):SetText("Exit"):CenterX():SetY(50)
button.OnClick = function()
panel:SetVisible(false)
end