Suggested this a couple of days ago but guess it got overlooked. I have a heap of variables where 2 triggers for each variable sets the status of that variable to either 'on' or 'off', and then an alias can call a quick list to world.note me which variables are set to off only. The problem (if you can call it a problem) is that when using triggers to send direct to variable requires putting the variable name as the trigger label, and of course because you cannot currently have 2 triggers with the same label, this again neccessitates having one of each 'pair' of triggers call a sub-routine script instead. (This will also cause the same work around if aliases allow sending direct to variables too in the future, which is my other suggestion).
I know you can't allow 2 triggers to share the same label as this will cause issues with other scripts that enable/disable triggers. As a suggestion, would it be feasible to instead create a new field for the variable name within the trigger parameters so that multiple triggers (and aliases one day too I hope) can send direct to the same variable without needing to script a separate sub-routine for 1 of them?
It's not a biggie since the sub-routine method works fine, but it would make things a lot cleaner imho.
I know you can't allow 2 triggers to share the same label as this will cause issues with other scripts that enable/disable triggers. As a suggestion, would it be feasible to instead create a new field for the variable name within the trigger parameters so that multiple triggers (and aliases one day too I hope) can send direct to the same variable without needing to script a separate sub-routine for 1 of them?
It's not a biggie since the sub-routine method works fine, but it would make things a lot cleaner imho.