SetPoint Issue #516


  • Defect
Open
  • LunaEclipse73 created this issue Aug 1, 2019

    12x Ace3\AceGUI-3.0\AceGUI-3.0-39.lua:339: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: AceGUI30Button2:SetPoint.
    [C]: in function `SetPoint'
    Ace3\AceGUI-3.0\AceGUI-3.0-39.lua:339: in function `SetPoint'
    AzeriteForge\Utilities\Frames.lua:639: in function `UpdateBagDataMenu'
    AzeriteForge\AzeriteForge-1.6.2.lua:1013: in function `?'
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:119: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:119>
    [C]: ?
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:29: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:25>
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:64: in function `Fire'
    Ace3\AceEvent-3.0\AceEvent-3.0-4.lua:120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

  • LunaEclipse73 added a tag Defect Aug 1, 2019
  • LunaEclipse73 posted a comment Aug 1, 2019

    I have received this error originating from several different addons, its definitely related to the Ace3 library and not the addons themselves.  Only started after 8.2 was released.  Also I installed Ace3 release 1224 as a standalone addon so that I could determine that it was not just a lack of using updated libraries by the addon authors.


    Edited Aug 1, 2019
  • nevcairiel posted a comment Aug 2, 2019

    The error you are listing in the original post seems like its related to how AzeriteForge does things. If you add a button to a layout and then still call SetPoint on it individually, ´there is nothing AceGUI can do for you - either position it yourself, or put it into a layout, not both.

     

    Also, its entirely feasible that more then one addon is doing things wrong.


    Edited Aug 2, 2019
  • LunaEclipse73 posted a comment Aug 2, 2019

    Okay, I reported it because I had seen the same error from at least 3 of my addons, I use Ace3 libraries in my own personal addon and have no issues, so as you said, they may have just coded it poorly.  However with multiple addons triggering the error I figured it was best to report it.


To post a comment, please login or register a new account.