Would it be possible to hide a panel when entering combat? Unfortunately, I am not a "scripter". I copied the party frame script from the first page. Works great. Love the new updates and keep up the good work!
Probably a noob question but I followed the pdf guide on how to make a gradient effect panel and I had it all set up and everything. When I hit lock frames, the top and bottom gradient borders disappeared. I rl'd and now I can't get those borders back. What's happening?
Probably a noob question but I followed the pdf guide on how to make a gradient effect panel and I had it all set up and everything. When I hit lock frames, the top and bottom gradient borders disappeared. I rl'd and now I can't get those borders back. What's happening?
I can't see any reason why changing the lock settings would affect panel visibility. Maybe you did something else on accident? double-check your parent and anchor settings. It's possible you're parented to a frame that doesn't exist or is hidden, or that your anchor settings in combination with your horizontal/vertical positioning has the eePanel offscreen.
Quote from cy-one »
How can i change the color of an Panel with the LUA-scripts?
I'm browsing through the code, but its difficult to find... for me :)
If you don't want a gradient, just use the same colors red/blue/green/alpha values
Quote from Slice »
Would it be possible to hide a panel when entering combat? Unfortunately, I am not a "scripter". I copied the party frame script from the first page. Works great. Love the new updates and keep up the good work!
You'll need to get a script to do this. It would be similar to the raid-hiding script, except you'd have to listen for PLAYER_REGEN_ENABLED, and PLAYER_REGEN_DISABLED to tell you when you're in and out of combat. If you need help writing a script, you might be able to find help in the Developer's Corner. I don't have the time to write everyone's scripts, sorry.
Would it be possible to hide a panel when entering combat? Unfortunately, I am not a "scripter". I copied the party frame script from the first page. Works great. Love the new updates and keep up the good work!
[2007/08/29 20:57:28-1590-x1]: eePanels2-2.0\core.lua:1844: attempt to index field 'background' (a nil value)
AceAddon-2.0-46764 (Ace2):927: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:920>
<in C code>: ?
AceEvent-2.0-44693 (Ace2):262: in function `TriggerEvent'
AceEvent-2.0-44693 (Ace2):955: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:948>
Getting this error on log-in. Attempting to create a new panel results in its own errors, and I can't right click on a newly created panel.
Error upon panel creation:
[2007/08/29 20:58:39-1590-x1]: eePanels2-2.0\core.lua:1471: attempt to concatenate field 'name' (a nil value)
eePanels2-2.0\core.lua:579: in function `CreateMenus'
eePanels2-2.0\core.lua:527: in function `CreatePanel'
eePanels2-2.0\core.lua:208: in function `func'
Dewdrop-2.0-46777 (DewdropLib):710: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:649>
Error upon right clicking on a newly created panel:
[2007/08/29 20:59:19-1590-x1]: eePanels2-2.0\core.lua:1652: Dewdrop-2.0: Bad argument #2 to `FeedAceOptionsTable' (table expected, got nil)
Ace2\AceLibrary\AceLibrary.lua:100: in function <Interface\AddOns\Ace2\AceLibrary\AceLibrary.lua:53>
(tail call): ?:
Dewdrop-2.0-46777 (DewdropLib):1262: in function `FeedAceOptionsTable'
eePanels2-2.0\core.lua:1652: in function <Interface\AddOns\eePanels2\core.lua:1652>
Dewdrop-2.0-46777 (DewdropLib):1872: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:1821>
Dewdrop-2.0-46777 (DewdropLib):2757: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:2716>
Dewdrop-2.0-46777 (DewdropLib):2973: in function `Open'
eePanels2-2.0\core.lua:1649: in function `ShowPanelMenu'
eePanels2-2.0\guideFrame.lua:67: in function `MouseDownListener'
eePanels2-2.0\guideFrame.lua:51: in function <Interface\AddOns\eePanels2\guideFrame.lua:51>
Looks like one of your panel's data values got fubar'd somehow. If you know what panel is messing up, you can type /script eePanels2:RemovePanel(PANELNUMBER) and then do a /reload and see if that helps. Backup your eePanels2.lua saved variables first.
What would be more helpful is a detailed list of what you did exactly leading up to that.
Looks like one of your panel's data values got fubar'd somehow. If you know what panel is messing up, you can type /script eePanels2:RemovePanel(PANELNUMBER) and then do a /reload and see if that helps. Backup your eePanels2.lua saved variables first.
What would be more helpful is a detailed list of what you did exactly leading up to that.
I have no panels as I've reset profile and also deleted my saved variables after experiencing those errors in order to troubleshoot. It didn't alleviate the problem.
As far as what led to these errors: I started rapidly creating new panels from the Global Setting (I believe I created 16) in order to begin a template I had in mind. The addon seemed to break after that.
logout of wow, go into your saved variables folder and delete anything that has eePanels in the name. If you still have problems, let me know. Your database is somehow corrupted.
Also, i've hammered the create panel button before and created dozens of panels and never had this occur.
I can't see any reason why changing the lock settings would affect panel visibility. Maybe you did something else on accident? double-check your parent and anchor settings. It's possible you're parented to a frame that doesn't exist or is hidden, or that your anchor settings in combination with your horizontal/vertical positioning has the eePanel offscreen.
Hmm well I got it back by changing the anchor to center and then back to the bottom but the width of it goes all the way across the screen. I have it at 100% but its not setting the width to the width of the parent.
And another question, how can I get the gradient to fade the other way?
/run eePanels2.db.profile.panels[35].background.frame:SetTexture(1,1,1,1)
Doesn't change anything on a mintgreen and fully transparent eePanel :(
I tested these and they work, but I made a small mistake in the second script (you have to tell it if it's horizontal or vertical). You can call them both, as long ast you call SetTexture after SetGradientAlpha. If you do this, make the first four colors in SetGradientAlpha the same color as SetTexture. If your panel is in gradient mode, you'll need to call SetGradient.
Would it be possible to hide a panel when entering combat? Unfortunately, I am not a "scripter". I copied the party frame script from the first page. Works great. Love the new updates and keep up the good work!
THIS:Show()
-- Hide panel ooc
function eePanels2:PLAYER_REGEN_DISABLED()
THIS:Hide()
end
-- Hide panel ic
function eePanels2:PLAYER_REGEN_ENABLED()
THIS:Show()
end
-- Ace2 event listeners; can't do this in more than one script
eePanels2:RegisterEvent("PLAYER_REGEN_DISABLED")
eePanels2:RegisterEvent("PLAYER_REGEN_ENABLED")
That is the exact code I ended up using.
I have a panel for an infinibar that I hide during combat, the script above hides the panel.
I played with eepanels2 a little this morning before I head for work, everything seems to be much easier than eepanel1, thanks for that ee.
I just have one probably silly question:
Any one else having an issue with coloring? I try to make the panels match as close as possible, however, when i make a 3rd or 4th "identical" panel it's "darker" than it should be. Anyone have any clue as to why? :/
Unfortunately, I can't get non-ace2 event hooks to work. I think it's because the normal WoW API requires OnEvent scripts to be set when the addon is loaded,which I don't do. Thus, if you want to register events you'll need to do so through the ACE2 event handling system.
Are you sure about this? And how does Ace2 handle registering events after this point then??
Oh I reread it. I see. Maybe you could take a look at how AceEvent handles scripts from multiple addons and use a similar system to handle the scripts for each frame.
Edit: Either I'm reading this wrong or you're mistaken. I just created a new frame, registered all events to it, and set an OnEvent script handler with :SetScript from the chatbox, so it was obviously long after any addons loaded, and it worked just fine. What problem are you having setting OnEvent scripts with the frames?
Took the step and removed old version today and installed this new one. I didn't have that many panels, and it should be easy to recreate them. Great work on the update.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Thanks
I'm browsing through the code, but its difficult to find... for me :)
I just wanted to say, eepanels2 is epic level win!
I can't see any reason why changing the lock settings would affect panel visibility. Maybe you did something else on accident? double-check your parent and anchor settings. It's possible you're parented to a frame that doesn't exist or is hidden, or that your anchor settings in combination with your horizontal/vertical positioning has the eePanel offscreen.
eePanels2.db.profile.panels[PANELNUMBERHERE].background.frame:SetTexture(redValue, greenValue, blueValue, alphaValue)
eePanels2.db.profile.panels[PANELNUMBERHERE].background.frame:SetGradientAlpha(redValue, greenValue, blueValue, alphaValue, gradientRedValue, gradientGreenValue, gradientBlueValue, gradientAlphaValue)
If you don't want a gradient, just use the same colors red/blue/green/alpha values
You'll need to get a script to do this. It would be similar to the raid-hiding script, except you'd have to listen for PLAYER_REGEN_ENABLED, and PLAYER_REGEN_DISABLED to tell you when you're in and out of combat. If you need help writing a script, you might be able to find help in the Developer's Corner. I don't have the time to write everyone's scripts, sorry.
I did the opposite on this thread: http://www.wowace.com/forums/index.php?topic=8155.0
The reply code by JRCC worked the way you want it to work (shows up in combat).
/run eePanels2.db.profile.panels[35].background.frame:SetTexture(1,1,1,1)
Doesn't change anything on a mintgreen and fully transparent eePanel :(
Getting this error on log-in. Attempting to create a new panel results in its own errors, and I can't right click on a newly created panel.
Error upon panel creation:
Error upon right clicking on a newly created panel:
This is the latest revision of eePanels2
What would be more helpful is a detailed list of what you did exactly leading up to that.
I'll find out later.
I have no panels as I've reset profile and also deleted my saved variables after experiencing those errors in order to troubleshoot. It didn't alleviate the problem.
As far as what led to these errors: I started rapidly creating new panels from the Global Setting (I believe I created 16) in order to begin a template I had in mind. The addon seemed to break after that.
Also, i've hammered the create panel button before and created dozens of panels and never had this occur.
Hmm well I got it back by changing the anchor to center and then back to the bottom but the width of it goes all the way across the screen. I have it at 100% but its not setting the width to the width of the parent.
And another question, how can I get the gradient to fade the other way?
To flip the gradient, simply swap the background color and gradient color (and their alphas/opacities).
I tested these and they work, but I made a small mistake in the second script (you have to tell it if it's horizontal or vertical). You can call them both, as long ast you call SetTexture after SetGradientAlpha. If you do this, make the first four colors in SetGradientAlpha the same color as SetTexture. If your panel is in gradient mode, you'll need to call SetGradient.
eePanels2.db.profile.panels[PANELNUMBERHERE].background.frame:SetGradientAlpha("HORIZONTAL" or "VERTICAL", redValue, greenValue, blueValue, alphaValue, gradientRedValue, gradientGreenValue, gradientBlueValue, gradientAlphaValue)
eePanels2.db.profile.panels[PANELNUMBERHERE].background.frame:SetTexture(redValue, greenValue, blueValue, alphaValue)
That helps a lot, thanks!
THIS:Show() -- Hide panel ooc function eePanels2:PLAYER_REGEN_DISABLED() THIS:Hide() end -- Hide panel ic function eePanels2:PLAYER_REGEN_ENABLED() THIS:Show() end -- Ace2 event listeners; can't do this in more than one script eePanels2:RegisterEvent("PLAYER_REGEN_DISABLED") eePanels2:RegisterEvent("PLAYER_REGEN_ENABLED")That is the exact code I ended up using.
I have a panel for an infinibar that I hide during combat, the script above hides the panel.
I just have one probably silly question:
Any one else having an issue with coloring? I try to make the panels match as close as possible, however, when i make a 3rd or 4th "identical" panel it's "darker" than it should be. Anyone have any clue as to why? :/
Are you sure about this? And how does Ace2 handle registering events after this point then??
Oh I reread it. I see. Maybe you could take a look at how AceEvent handles scripts from multiple addons and use a similar system to handle the scripts for each frame.
Edit: Either I'm reading this wrong or you're mistaken. I just created a new frame, registered all events to it, and set an OnEvent script handler with :SetScript from the chatbox, so it was obviously long after any addons loaded, and it worked just fine. What problem are you having setting OnEvent scripts with the frames?