WowAce

tag 2.1.0.9
1a83f72c6969f0d0556a4ac48a6c89e42137b0d5
Benjamin Staneck <staneck@gmail.com>
2015-09-06 21:35:25 +0200

--------------------

Benjamin Staneck:
    - Revert "Disable WeakAuras.FixGroupChildrenOrder() completely to see if we even need it and further fight strata bugs/taint."
    This reverts commit ea3095f98360250002251a53638d72875bb84e40.
Infus:
    - Animate: Don't use a new table in WeakAuras.Animate
    Reusing the table leads to less garbage
    
    Ticket-number: 410
    - BigWigs Timer trigger: Fix addon option
    Ticket-number: 412
    - Fix duplicate moving the list around
    WeakAuras.NewDisplayButton() in addition to adding a new button
    also scrolled to that button and started the renaming.
    
    Since in the duplicate code path we first call NewDisplayButton and
    then add the new aura to the right group, we first scrolled to
    a mostly random position.
    
    Fix that, by removing the code to pick and edit a button from
    NewDisplayButton and move that to a separate new function
    WeakAuras.PickAndEditDisplay
    
    Call that function at the end of duplicate.
    
    It might be necessary to add a call to WeakAuras.PickDisplay or
    WeakAuras.PickAndEditDisplay from other code paths, I checked
    the common ones like New/Import/Add to group and remove from
    group and they seemed to work.
    
    Ticket-number: 404
    - WeakAuraOptions: Check for data.trigger.names being not nil
    Ticket-number: 408
    - Dbm Timer: Change Spell Id to Spell/Encounter Id
    And change the type to a string.
    
    Note: new locale string.
    
    Ticket-number: 409
    - Dbm Timer: Fix id trigger option
    Ticket-number: 407
    - BuffTrigger: Cope with GetUnitName(guid) returning nil
    By keeping the name unknown and rechecking next time again.
    
    I wonder whether we should remove the player from self.players
    if we repeately can't get their name.
    
    Ticket-number: 406