Trigger now has a new method Trigger:SetData and two new fields
Trigger.defaultData and Trigger.data
Whenever SetData is used it ensures that all the keys and values from
defaultData are present in the new data.
The data argument from Trigger:SetState has been removed and it will now
always use the Trigger.Data field for notifying indicators
MultiTrigger will pass on the data from the highest priority child
trigger.
Fix MultiTrigger
MultiTrigger didn't properly inherit from Trigger and reimplemented some
methods. This happened because it started out as a copy of Trigger
- The indicator will grab a frame from a pool
- Having a frame, it now uses a real border/edge
- There is a stacks number that can optionally be enabled
StatusTrigger will trigger if a status activates (or reaches a certain
activation # of auras). This is an abstraction provided by AuraList
which keeps track of which auras belong to which statuses.
Added type annotations to all touched files
The base Trigger class is now responsible for inverting the trigger
state and also for signaling trigger activation to the target/indicator.
In addition the following non-function changes also occured:
- The triggers moved into their own directory
- The trigger code has been annotated to help lua-language-server
deduce type information
- AuraTrigger was moved into its own file
All these changes should make future development of other triggers easier
