2.4.3-10-g3c457ff-alpha

Details

  • Filename
    WeakAuras-2.4.3-10-g3c457ff-alpha.zip
  • Uploaded by
  • Uploaded
    Jun 18, 2017
  • Size
    3.39 MB
  • Downloads
    2,458
  • MD5
    2512146586ef7e61771093ec88876131

Supported WoW Retail Versions

  • 7.2.5

Changelog

Changes since tag 2.4.3

commit 3c457ff6956baf65f4abd7ac66966a4af268ff63
Author: Infus <[email protected]>
Date:   Sun Jun 18 23:27:46 2017 +0200

    Tweak Text Replacements again

    Make the code try one character replacements after failing to
    find a variable in state. This is what the old code essentially did.

    Ticket-Nr: 980

commit 28faeaca45d586bd98db3e5bcec26049e3249a7a
Author: Infus <[email protected]>
Date:   Sun Jun 18 02:07:50 2017 +0200

    Fix BigWigs triggers with spell id strings

    Ticket-Nr: 971

commit 1043ac708f450ba151512dbec1ab26dc398db0ae
Author: Infus <[email protected]>
Date:   Sat Jun 17 22:23:36 2017 +0200

    Fix Power trigger after Destro fix

    UnitPowerDisplayMod is rather strange and returns 10 for lots of
    powertypes. Thus, introuduce two helper methhods:

    WA.UnitPowerDisplayMod which returns 10 for just Soul Shards.
    And WA.UseUnitPowerThirdArg which returns true for just Sould Shards.

commit aaeae1d3115ecbfa5861b48d1eb22d09db9b31aa
Author: Infus <[email protected]>
Date:   Sat Jun 17 21:56:47 2017 +0200

    Change how text replacements work

    Instead of trying all dynamic texts and all members of state,
    iterate the string once. And on finding a %, use all alphabetical
    characters after it. If that string is only one character look it
    up via dynamic texts. Otherwise look it up via the state.

    Since we are only iterating once, instead of many times this should
    also be faster than before.

    Note: This is not 100% backwards compatible, e.g. %pRage would
    previously replace the %p, this now requires a space.

    Ticket-Nr: 957

commit 873300b0404c3e71a47559a82c59e222c6d81912
Author: Infus <[email protected]>
Date:   Sat Jun 17 20:34:01 2017 +0200

    Fix invalid usage of "_operator" value in trigger

    If a user switches a trigger from a trigger type that has arg with
    a number/longstring tpye thus using a _operator to a trigger
    type that has a arg with the same name but of a different type
    that is not using the "_operator" the setting for the operator
    is still in the trigger data.

    Fix this by only using the stored _operator setting if the type is
    actually a number or a longstring.

    Ticket-Nr: 979

commit 80cdde889414a6f4180afa3c6eae2f9a0c88f707
Author: Infus <[email protected]>
Date:   Sat Jun 17 16:02:23 2017 +0200

    Improve performance on opening options with gigantic dynamic groups

    Pause/Resume dynamic groups around the showing of all loaded auras.

    Ticket-Nr: 978

commit c128b0bb92150d71a5967e77f101db1ff53f7ad6
Author: Infus <[email protected]>
Date:   Fri Jun 16 18:16:28 2017 +0200

    Conditions: Run Custom Code: Fix error on "Expand Text Edtitor"

    Also remove some todos in that area that are already done.

    Ticket-Nr: 974

commit 01712f63e4fddc1cdb0cc260f2f5e8182fc562d3
Author: Infus <[email protected]>
Date:   Fri Jun 16 16:47:57 2017 +0200

    Change IsSpellKnown/Talent Selected for new Legendaries

    Use IsPlayerSpell in addition to IsSpellKnown. And use the 11th return
    from GetTalentInfo() in addition to the 4th.

    Ticket-Nr: 970

commit c4d0e26ca7a3e729f172b31b771adfb585bcd194
Author: Infus <[email protected]>
Date:   Fri Jun 16 16:43:48 2017 +0200

    Templates: Landslide talent was wrong

commit 29b502581341afdab2b1f7482b2e53365164cfc1
Author: Infus <[email protected]>
Date:   Fri Jun 16 16:43:19 2017 +0200

    Fix Destruction Warlocks

    The previous fix was incomplete.