• Announcements

    • Maniq

      Forum Rules (Updated 3/22/14)   07/14/10

      Welcome to the Elitist Jerks forums, a WoW discussion forum targeted towards topics regarding high-end raiding and analysis of game mechanics. We ask you to take a few minutes to read the following before making use of these forums.   First, a point of clarification. The name of these forums is not intended ironically; we have high standards for the discussion that occurs herein, and we're quite unapologetic about it. If you feel our rules are stupid or arbitrary, we don't really care. If you don't wish to follow them, you're welcome to return to the official Blizzard forums.   Following is a brief listing of our forum rules; note that it is by no means exhaustive, as in our experience people are quite innovative in finding new ways to be stupid. These are simply a set of guidelines to get you started in the right direction. If you follow them, you will generally do fine here; however, if you concoct some creative new form of stupidity, our moderators feel no need to restrain themselves in letting you know. All posters are to make an effort to communicate clearly. In particular, all posts should be made in a reasonable approximation of proper English. We realize that a significant number of you are not native speakers, and we do not expect perfection: merely effort. Please obey basic rules of capitalization and punctuation, avoid chatroom abbreviations ("lol", "imo", "u", and the like), and pay at least minimal attention to sentence and paragraph structure. This includes not starting a new paragraph for each sentence. All opinions should be stated as succinctly as possible. Do not make multiple consecutive posts; rather, multi-quote and include all your ideas in a single post. Do not quote huge blocks of text to add a short reply; instead, quote only what you need to to make your point. Do not break a single quoted reply into multiple blocks; doing so needlessly lengthens your post without aiding its readability. And don't provide unnecessary backstory: if it isn't relevant to the question you're asking or the point you're making, we don't need to know about it. All discussion should be both polite and civil. Trolling or flaming in any form is forbidden. Just because someone disagrees with you does not mean they are stupid or on drugs and their personal hygiene isn't really relevant to the discussion. Regardless of the merit (or lack thereof) of your argument, it should be made in a way that is neither insulting nor condescending. Whining in any form is forbidden. Blizzard is not incompetent or stupid and they are not intentionally screwing you over and neither is anyone else. If all you're going to do is complain, don't bother posting. Threads should be started if and only if there is some reasonable topic to discuss. If the issue you wish to discuss is covered in an existing thread, use it rather than creating a new one. If you are asking a simple question that you expect to have a simple answer, ask it in one of the "Simple Questions/Simple Answers" threads. But if you feel there is a topic of discussion not well-covered by existing threads, feel free to start a new thread to discuss it. Some sub-forums restrict new members from creating new topics unless they've made at least 10 approved posts, to prevent spamming or bad posts. If you really think it deserves a new thread before you have 10 posts, contact a moderator with your post content. Do not post unless you have something new and worthwhile to say. Do not bump, quote for truth, cross-post, or post only to say thanks. We don't want to hear your funny story about something that happened in your raid last night, your baseless speculation is unproductive, and your idea for a new ability really isn't that interesting. We don't care what gear you are hoping to get or just received. If you have an idea you'd like to share with the community, support it with analysis, testing, or both that indicates you've put some thought into it. (Note: Posting of a new untested spec falls under this rule, unless you have done the grunt work and have information to support your amazing new spec don't even bother posting it here.) Do not beg for hand-holding. These are forums for discussion and analysis, not for answering any question that you might happen to dream up. Search and read before posting--do not post a question unless you are fairly confident that the answer isn't widely known or easily attainable. In particular, we do not want to take a look at your armory or WWS to tell you what you're doing wrong and we're not interested in making your tough gear or spec decisions for you. We expect you to use the search function and also to read the first post as well as the last 5 pages of the thread you are posting in. Chances are your question has already been answered. Additionally, do not post asking for confirmation of a simulation result. If you think there is a problem with the Sim you are welcome to PM the author. All accounts must have a valid WoW profile. If you no longer play and have deleted all characters you used to have, you may select the "No WoW Account" option; otherwise, this information must be filled out for your main character. If you fail to observe this rule you'll be permanently banned from our forums. We do not permit anonymous posting. Do not sign your posts. People can see who you are from the profile printed to the left of each post, so signing your posts is redundant and simply takes up space. Similarly, you do not need to link your armory in your post, as if people wish to see it they can get it from your profile. Do not respond to terrible posts. Do not respond to a blatantly awful post (a post that is in clear violation of the rules) either in an attempt to moderate them or to answer a question they posed. Your post will just be warned/infracted and removed with the post you are replying to. If you feel that a post is in violation of these rules, please report it and the moderators will deal with it as we feel is appropriate. No Advertising. Do not make posts solely for the purpose of advertising your site/blog/twitch/etc. You may post such things if it's relevant and adds to discussion at hand. If you have information to share, share it here with a link back to your blog or whatever. Do not post "I have information, come to my site to get it". That will result in an immediate infraction and post removal. Also, we will remove any link to a site that violates a games TOS/EULA such as gold selling sites.

      If you violate a forum rule, you will receive an infraction. Most infractions are worth one point, although we reserve the right to give you more at any time if we feel you deserve them. If you accumulate too many infraction points, you will receive an automatic (usually temporary) ban which revokes your posting privileges, as follows: 3 Points - 1 Day 5 Points - 3 Days 8 Points - 1 Week 10 Points - 1 Month 15 Points - Permanent

      Familiarize yourself with The Banhammer, an archive of all infractions given by the moderators here; it will give you some examples of what not to do. Also feel free to take a gander over The Dung Heap, which will give you a good idea of what these forums would look like if we weren't such jerks.   Thank you for joining the discussion!


  • Content count

  • Joined

  • Last visited

About Gethe

  • Rank
    Glass Joe
  • Birthday 08/29/88

WoW Profile

  • Character Name Gethe
  • Guild Old Skool
  • Alternate Characters Æthos - Orc Death Knight - Blood/Frost
    Kazzix - Goblin Priest - Disc/Shadow
  1. [Fixed] Custom timer skins

    So i am a derp, I was using DBT:SetSkin instead of DBM.Bars:SetSkin. That's why self didn't have the correct tables. Thank you for your patience and help.   I'll see about adding independant Icon sizing if you don't want to. This is a crucial part of my skin.
  2. [Fixed] Custom timer skins

    It worked! I made it not LoD, and commented out the errorhandler for not being LoD (it wouldn't load otherwise). Then made a check if DBM-SBT was loaded before calling SetSkin(). LoadOptions didn't even need to be called. (note: This was with r11231) Thanks for your help!   That said, I would appreciate it if my second edit with the icons and frame would be applied. This would allow for icons that are larger than the bar height. Then again that would likely mess with the default skin, so for proper support there would likely need to be a specific option for that.
  3. [Fixed] Custom timer skins

    I had thought of that, but DBM-StatusBarTimers is already a Dep for DBM-Core so i figured having just DBM-Core listed would be fine. Regardless, I reverted the changes to self and added SBT as a ReqDep. Got this error: 1x DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:367: attempt to index field "options" (a nil value) DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:367: in function "SetOption" DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:983: in function "SetSkin" DBM-RealUI\Skin.lua:34: in main chunk <in C code> nibRealUI-8.0 r28\Skins\DBM- in function "Skin" nibRealUI-8.0 r28\Skins\DBM- in function <nibRealUI\Skins\DBM.lua:105> (tail call): ? <in C code> <string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5 (tail call): ? AckisRecipeList-2.6.2\libs\AceAddon-3.0\AceAddon-3.0-12.lua:558: in function "EnableAddon" AckisRecipeList-2.6.2\libs\AceAddon-3.0\AceAddon-3.0-12.lua:571: in function "EnableAddon" AckisRecipeList-2.6.2\libs\AceAddon-3.0\AceAddon-3.0-12.lua:651: in function <AckisRecipeList\libs\AceAddon-3.0\AceAddon-3.0.lua:636> <in C code> FrameXML\UIParent.lua:306: in function "UIParentLoadAddOn" FrameXML\UIParent.lua:380: in function "TimeManager_LoadUI" FrameXML\UIParent.lua:740: in function <FrameXML\UIParent.lua:705> <in C code> Locals: self = <table> { GetOption = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:375 UpdateBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:547 SetAnnounceHook = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1066 GetSkins = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1035 GetTextures = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1039 ShowMovableBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:804 GetDefaultOption = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:379 SetOption = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:356 CreateDummyBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:485 New = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:312 LoadOptions = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:341 RegisterSkin = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:955 CreateBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:404 SavePosition = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:787 ShowTestBars = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:562 GetFonts = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1043 GetBarIterator = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:521 CancelBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:537 SetSkin = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:969 GetBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:529 ApplyStyle = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:854 } id = "RealUI" skin = <table> { loaded = true defaults = <table> { } name = "RealUI" } totalBars = 0 skins = <table> { RealUI = <table> { } DefaultSkin = <table> { } } unusedBars = <table> { } pairs = <function> defined =[C]:-1 options = <table> { EndColorG = <table> { } Scale = <table> { } HugeBarsEnabled = <table> { } TextColorB = <table> { } Flash = <table> { } HugeBarYOffset = <table> { } HugeWidth = <table> { } TimerX = <table> { } Texture = <table> { } ExpandUpwards = <table> { } Spark = <table> { } Width = <table> { } HugeTimerPoint = <table> { } EnlargeBarsTime = <table> { } TextColorG = <table> { } HugeBarXOffset = <table> { } IconLeft = <table> { } Height = <table> { } Skin = <table> { } IconRight = <table> { } BarYOffset = <table> { } Template = <table> { } FontSize = <table> { } HugeScale = <table> { } ClickThrough = <table> { } FillUpBars = <table> { } EnlargeBarsPercent = <table> { } TextColorR = <table> { } StartColorG = <table> { } HugeTimerY = <table> { } HugeTimerX = <table> { } EndColorR = <table> { } TimerY = <table> { } TimerPoint = <table> { } Font = <table> { } Style = <table> { } DynamicColor = <table> { } StartColorB = <table> { } StartColorR = <table> { } BarXOffset = <table> { } EndColorB = <table> { } } Then i tried doing a hard check for DBM-SBT before loading the skin and i got this when opening the options: 1x DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:395: CreateFrame(): Couldn"t find inherited node "RealUISkinTimerTemplate" <in C code> DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:395: in function <DBM-StatusBarTimers\DBT.lua:389> DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:419: in function "CreateBar" DBM-StatusBarTimers-5.4.13-37-g529e77c\DBT.lua:487: in function "CreateDummyBar" DBM-GUI\DBM-GUI-5.4.13-37-g529e77c.lua:1695: in function "?" DBM-Core\DBM-Core-5.4.13-37-g529e77c.lua:1798: in function "LoadGUI" DBM-Core\DBM-Core-5.4.13-37-g529e77c.lua:1498: in function "?" FrameXML\ChatFrame.lua:4315: in function "ChatEdit_ParseText" FrameXML\ChatFrame.lua:3969: in function "ChatEdit_SendText" FrameXML\ChatFrame.lua:4008: in function "ChatEdit_OnEnterPressed" <string>:"*:OnEnterPressed":1: in function <string>:"*:OnEnterPressed":1 Locals: self = <table> { announceHook = <function> defined @Interface\AddOns\DBM-Core\DBM-Core.lua:4915 smallBars = <table> { } options = <table> { } defaultOptions = <table> { } mainAnchor = <unnamed> { } secAnchor = <unnamed> { } hugeBars = <table> { } bars = <table> { } } frame = nil unusedBars = <table> { } fCounter = 1 setupHandlers = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1214 It may be relevant to mention that the skin addon is LoadOnDemand, and DBT will yell at you and not load it if it isn't. Though since it is LoD none of the associated options or templates get created, but DBT needs the template to load since i had already successfully made that change with my previous edits.
  4. [Fixed] Custom timer skins

    Ok, I managed to get this to work with a couple tweaks to DBT.lua   I changed a few uses of self to reference DBM.Bar instead. The icon and frame sizing lines were commented out so that it can support narrow bars with larger icons. The huge bar scaling still works properly as far as I can tell.   This may not be the most clean or ideal solution, as i'm not all that familiar with the code, but it works and I'm not getting any errors. DBT.lua
  5. [Fixed] Custom timer skins

    Thanks for the response. I tried it out with the new build, but i'm now getting a new error. 1x DBM-StatusBarTimers-5.4.13-36-ga5863c3\DBT.lua:367: attempt to index field "options" (a nil value) From what I can tell it's an improper use of "self", which in this case is referring to the table "DBT". The only things in the DBT table are the functions created in the file (as viewed from the addon Luabrowser), thus when it tries to call self.bar or self.options it fails.   You wouldn't have seen it fail before because it isn't used at all in DBM, just for the API.   For additional context and in the case that i'm flat out wrong (very possible), I have attached what i'm working on. DBM-RealUI.zip
  6. I'm making a timer skin using the DBT api, but I can't seem to get it to work. There isn't any skin option in the GUI, and when I try to set it with  /run DBT:SetSkin("MyDBMSkin") I get this error: 2x DBM-StatusBarTimers-5.4.13-35-gf2d0746\DBT.lua:522: bad argument #1 to "pairs" (table expected, got nil) <in C code> DBM-StatusBarTimers-5.4.13-35-gf2d0746\DBT.lua:522: in function "GetBarIterator" DBM-StatusBarTimers-5.4.13-35-gf2d0746\DBT.lua:970: in function "SetSkin" <string>:"DBT:SetSkin("MyDBMSkin")":1: in main chunk <in C code> FrameXML\ChatFrame.lua:2036: in function "?" FrameXML\ChatFrame.lua:4315: in function "ChatEdit_ParseText" FrameXML\ChatFrame.lua:3969: in function "ChatEdit_SendText" FrameXML\ChatFrame.lua:4008: in function "ChatEdit_OnEnterPressed" <string>:"*:OnEnterPressed":1: in function <string>:"*:OnEnterPressed":1 Locals: self = <table> { GetOption = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:375 UpdateBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:543 SetAnnounceHook = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1056 GetSkins = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1025 GetTextures = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1029 ShowMovableBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:800 GetDefaultOption = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:379 SetOption = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:356 CreateDummyBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:485 New = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:312 LoadOptions = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:341 RegisterSkin = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:951 CreateBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:404 SavePosition = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:783 ShowTestBars = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:558 GetFonts = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:1033 GetBarIterator = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:521 CancelBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:533 SetSkin = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:964 GetBar = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:525 ApplyStyle = <function> defined @Interface\AddOns\DBM-StatusBarTimers\DBT.lua:850 } pairs = <function> defined =[C]:-1 This is without anything other than bugsack/grabber (plus DBM and my addon ofc.) I am using the alpha DBM.