Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After changing the order of buttons, Artisan should automatically change any references to those buttons in Multiple Event action fields #1530

Open
upatamby opened this issue Apr 2, 2024 · 0 comments

Comments

@upatamby
Copy link

upatamby commented Apr 2, 2024

I'm quite new to Artisan but I'm very happy with what I discovered so far.
While playing around with events and buttons, I discovered the Action type called Multiple event which is a great option to automate things. But the problem is that when I use this option it becomes very hard to change the order of the buttons, because after every single change I also have to change any reference to the changed button numbers. Can't this be done automatically?

The 'simplest' solution would be if references to button numbers are updated automatically after any change in the sequence of the buttons.
Another solution would be if buttons get a unique identifier that can be used in stead of those numbers.
Ik would be nice of I could name my own identifiers, like "cooling_on", "cooling_off", etc. so the references become readable.
But any solution would be welcome.

@upatamby upatamby changed the title Auto Renumber Multiple Event numbers when changing order of Buttons At Multiple events: auto change references when changing order of Buttons Apr 2, 2024
@upatamby upatamby changed the title At Multiple events: auto change references when changing order of Buttons After changing the order of buttons, Artisan should automatically change any references to those buttons in Multiple Event action fields Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants