cast triggers act as if "inverse" is enabled by default
Causese opened this issue ยท 3 comments
Is there an existing issue for this?
- I have searched the existing open and closed issues.
Description
cast triggers act as if "inverse" from display section is enabled by default.
this did not use to be the default behaviour and kind of forces everyone to adjust their stuff
i included a screenshot. seems to even affect newely created WAs
WeakAuras Version
5.12.5
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
EU
Tested with only WeakAuras
- Yes
Lua Error
No response
Reproduction Steps
- create a player/unit info cast trigger or import mine for blizzard cast
- cast something
- see how its ugly
Last Good Version
No response
Screenshots
Export String
!WA:2!1z1tVTXXvCTMP1aSOfYSnQrUUTBcQtLsvPSPRKdsBAcxjsl5Q)WSCDKsUqo7Ud5oXl3z8mZQ)HEj8qTApKcqGICkOi8CpXVafqa5(aIETx0H(bqFbsFZSlPKITjajN5nV593FV59SQxQxPWsHNU0qsanPjnLhGVZm(hI6s3C9bF6J34WTpOUZEUb0yk)XfGp8J3TthbwAncLeer5nOKeP)A12XRM74aknoKEysZdjmC7kP8y2TJKsM49wEzTmltOlh2HJiHpy5h(7C06SDFjN0TlMl(rVnpF5P)0HcgooEhupS429DIjNCcIhoaLYrjAAfz3kvGB1fNG5KGMr0d3nP94RT9CH5V1YTO(A(ttiY2xaRQDekq2uRIndJggI9t70X7ygMVrv3TR)KTgmv9wosGUJ(MSsAzG8fuU)gyu820qC7ZfP(4dWjYMGiihnQ1AvB61QPxvxVZ1SFPF0wDBFwm6ym31CbN1qc5zAxYWdjuuCmheBZPQE81eq7(ImdwuKdhOjfD(Lw01TMgCmynUnBuBRTgOzsYrbpTTBw0BqAsEKgcKqKGCa2lBVwk)RzUasPyEck(JH0cHM83V4PymRkO)aPlssOrde44oMuV6Mq8tGKGFiXT5hKDJ)XqWsCXDHLItMtn)yyRpybD500KWtFD28s8rYwMF6q59qYwj5lCsOj4xY5I8fQvhm9SrRBsDc7ntcyZAilIqq(EndE1YYQW5zuNyUovFI3USFSHikvsbbsc2JekJCQcBVitJKJWHgIF(4mu(NKd6pZC(NLkKKohdUoNkb32di6SZU7utnphCunpdnmEzzZGCxjrEwvobfBVdIZPhYkDfJEIsgBODiLhUhhX6Vx(IXtfHbQU7t82AZDQL72xPy8m4KAUTC21ZB3TVMc2)AkqlPMKtWVzUpU)18XdicIFmU9P)m2B(c5cwljPhUfJJdi60Db1dvRQE336UmM9RI5E0WwgmI63R(dQ3x9hvFWNZ(vVkUJXDrbh3QtmLYJuvv3u5Ow7LGky5lC13kKT4RsEHhdqFsqlzehdVmehAPMxTUAxlvnt(rvNnBDo5e7pkffcMjY2Zt9HwQnSuVNbhP2u9yLBB12GP8NuBX(fVknLTZs14bQpYsTIA1oJ9HmiM3IMfFvZpqxnyODw(rxcuopNsE8pAu(ECyxm7wnFwkIJTRNghBVxerINCSasKFV)34UX0dRZXplfNeCCJx7ELRSsgMuFWzWdbpkoV4ODFnjnsYTba3Jnx1lIe80eSq041Qu((RmstBcQCq3jx1yNNP3UUUQxN)nCU)v5SzakgxWrVS9q9VBHt6kJEDZHBraLCxdzhJ9hD6px1CkksO8UkkrNhEYuqGA)PPKp1KeZH4xde)dNMwvpcYHxJLChkEgLBKjRcPt12SBT5o7mTSXDZhTHNgDa5V8m5hR270FPzVXkzZE3S(gRfJeInHoztSkGrTnEf73R9lb5gm99SPW7F9lW03rfxEfW043zgdg(zlnZLE7Ny8ga128selB2R6ABvRUNoYbr0glQDSp0Ypct6gj)ANykkSJUbzla)aVudDbiHr(sivMiNZTxASKu0nqBoZP(ZfD0De0lgDf2DQ8UvUNJgpQpHnliTQH6xmXH4WTrhfbTR0Jz4t6XOC5aucPNbeTQRqI4Y6NHrcCtj3GxUj4IRoomhN1s3mMlWqOiu0xZNgaRw1PhIKC6C(MYi3n(G)7x9v)7V9B)g1PQ)6aumlcPzBOzvJ0yboJrNPmMT)rt3NDP6PqxLVSd8Rw3lW40UWJhILSn25s2H4yjAXI2WNyka3TrjDJX2VV9uwTFh7kWxW)IkZilA)BTxiFT9Y2vYUkhd9otYKP9VXEHfYyrqswWiVfbI3FXLRSiiOCnItclA6QBmZiDiQ)Kq0nu)nOdP(qJpbrBDH4XfCn8A5N1XYQ0XwLoYYhEbhkfuFrwaOAHbM)1o(nuppFNo25hajqAVmHDub)oKeIiQU65M8JooRv73nztsIgYndbyst)G(tMpS9qDgKOTxrXZNeTYg)8DUZm3ym0AgQu3LLXbyDjDiDlYpk)fMlYQKRZHXzmMxZ1CRvBNrD0eaOd8(Db2pzI20TNxNiqWZPHT9f4EWqk(3V89k)WhmusdYhz5nSEEYBrczZcdh2Jb5r)8XoDoHs71OW9k)a1xwW9q9ybFTzwWjZwcdn5QBSvjLeokEdNME719XF2ZGrQs0YghXrgeKyv1F5TDf6jG42zb0(H0wgcrQ)zrhiOklokKi0ZjQR3FJV)xm3isswvpiH5gbldW10J4jAF2ehSg0BiQKWFLY3Vs5vkDW)z)))d
Ah that's an intentional behaviour change in 5.12, though I forgot about it in the release notes.
The cast trigger sets the "inverse" flag in the progress, because casts actually fill the progress instead of depeleting it, which is the inverse flag.
The icon region used to ignore the inverse flag, for unknown reasons. With the progress refactor I fixed that, so that all the regions observe the inverse flag.