Overachiever - achievement tools and tweaks

165 - Nil value :477

Message: Interface\AddOns\Overachiever\Overachiever.lua:477 attempt to index field 'AchievementFrame' (a nil value)
Time: 09/06/11 20:53:22
Count: 1
Stack: [C]: ?
Interface\AddOns\Overachiever\Overachiever.lua:477 in function <Interface\AddOns\Overachiever\Overachiever.lua:470

~

Above only happens once each time I log in and open up the achievements.

Name Description Size MD5
Overachiever.lua Patched to check for ... 46.9 KiB 7f217e309ecb...
User When Change
Maziel Sep 10, 2011 at 00:25 UTC

Added attachment Overachiever.lua

Maziel Sep 08, 2011 at 13:31 UTC Changed status from Waiting to Replied
Tuhljin Sep 06, 2011 at 17:55 UTC Changed status from New to Waiting
Maziel Sep 06, 2011 at 10:57 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 4 comments
  • Avatar of Maziel Maziel Sep 10, 2011 at 00:22 UTC - 0 likes

    My current solution is to revert back to using MoveAnything and I have modified your code:

    Overachiever.lua: local function AchievementUI_FirstShown_post()

      -- CHECK TO SEE IF MOVEANYTHING IS ENABLED
      MoveAnything_name, MoveAnything_title, MoveAnything_notes, MoveAnything_enabled, MoveAnything_loadable, MoveAnything_reason, MoveAnything_security = GetAddOnInfo("MoveAnything")
      
      if MoveAnything_enabled == 1 then
    	-- DO NOTHING AS MOVEANYTHING IS ENABLED
      else
    	if (orig_AchievementFrame_area) then
    	  UIPanelWindows["AchievementFrame"].area = orig_AchievementFrame_area
    	  AchievementFrame:SetAttribute("UIPanelLayout-area", orig_AchievementFrame_area);
    	  orig_AchievementFrame_area = nil
    	end
      end
    

    This modification has solved my problem.

    Last edited Sep 10, 2011 by Maziel
  • Avatar of Maziel Maziel Sep 10, 2011 at 00:04 UTC - 0 likes

    Ok Tuhljin, I found a solution to get rid of the error.

    I had to disable the MoveAnything option to move the Achievement Frame and then use your option to move and remember the frame position.

    This gives me the same outcome as I wanted but without the error. =)

    I am still wondering if there is a way that you could check for people using MoveAnything and if they have moved the AchievemeentFrame via MoveAnything, give them either a chat warning mentioning that OverAchiever can handle the movement, please remove AchievementFrame from MoveAnything or perhaps it is possible to automatically remove it from MoveAnything if detected and assign its own position based on where it was moved to.

    Just random thoughts, but at the end of the day, found the solution.

    == EDITED ==

    Looks like your OverAchiever is not remembering the position I told it to remember.... I thought I had a solution as mentioned above, but not it doesn't seem like it is remembering.

    Any thoughts?

    Last edited Sep 10, 2011 by Maziel
  • Avatar of Maziel Maziel Sep 08, 2011 at 13:31 UTC - 0 likes

    Howdy Tuhljin.

    What it is is MoveAnything.

    I have the AchievementFrame set to the middle of my screen (running hi res) via MoveAnything.

    http://wow.curse.com/downloads/wow-addons/details/move-anything.aspx

    And it works fine.

    Except when I have Overachiever running too.

    Overachiever doesn't like that I have moved the AchievementFrame I guess.

    Everything works, don't misunderstand, AchievementFrame loads up in the middle of the screen as I have set it via MoveAnything and your extras attach themselves perfectly and all work; but I get the above mentioned error because of it (once per load / reloadui)

    If I tell MoveAnything to not move the frame to the center and leave it in the default position, I get no errors from Overachiever.

    But that defeats the purpose of installing MoveAnything which does what it is meant to do, move frames.

    Is there anyway you can add a check for the position of the AchievementFrame set via MoveAnything and thus hopefully avoid the forementioned 477 (470) error from popping up?

    Cheers.

    I hope the above information helps you in reproducing the nil error.

    - Maziel

  • Avatar of Tuhljin Tuhljin Sep 06, 2011 at 17:54 UTC - 0 likes

    Please try with all other addons disabled. You'll likely notice no problem. Then, determine where the addon conflict lies by enabling your other addons one at a time or by using the process of elimination (half at a time, determine if it's one of those, disable half if so or enable half the others if not, and so on, until you've pinpointed which addons(s) cause conflict).

  • 4 comments

Facts

Last updated
Sep 10, 2011
Reported
Sep 06, 2011
Status
Replied - Someone has replied after waiting for more information.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees