Would it be beneficial to have the ability to have the same Run Actions button as a "run" icon at the end of rule machine & room lighting scripts? This way the code could be run simply by touching it vs. having to open the script and selecting the run action button contained within the script itself. See conceptual screen.
Although the run actions button within the code is great while developing / testing; once developed, I think it would add to the usability of the product / convenience if a green run button was automatically added right at the end of the name of the scripts.
It may be better to have it automatically placed at the end of the names (see examples) vs. adding another box next to the disable box. It would not be functionally applicable to the other applications and make sense and would add too much white space to those apps. However; that is certainly up to those much smarter than me to figure out.
Looking at it not only from a convenience standpoint, it may also help that the non-technical users of the software not be exposed to the code to run something. They just click on a run button :-).
Certainly something for the community to weigh in on and the developers to determine if helpful and even feasible. If so, then when it would be fit into their roadmap.
As always, thanks
1 Like
Hi harmony7,
Thanks for taking your time to respond! Replies below.
(1) Not so much sparing the user the labor to add but I was thinking it would improve the usability by automatically having the run action functionality (which is already within the script) added vs. having to open the rule or lighting app , having a separate activator device to maintain, etc. My experience with the activator device (although very limited) is that; when the link is clicked, it opens like the rule or light app, and you still have to take another action to act upon it. Whereas the proposal is that a single click will perform the function. From the "landing page" you could run the desired rule / room lighting function with a single click vs. 3 clicks.
(2) See above. If more information needed let me know. Again this is just my opinion :-).
(3) I am totally unaware of the level of effort, practically, or even its feasibility. That's why I noted early I would leave this area in the very well trusted and capable hands of the developers. If you are one of those folks then please accept my apologies.
(4) Absolutely. The less individuals have to click or "drill down" to perform a function; and as noted earlier, those less experienced or could feel overwhelmed or intimidated by code I would think the better. If someone can simply click run I believe (again my opinion only) the more likely they would find the app more "user friendly" to use.
Thanks again for your time!!
1 Like
Great idea! I am going to do this for a few that I run quite often!
Thanks for the feedback and suggestion!
1 Like
This can already be done in webCoRE.
If you click on the '3 dots' to the right of the piston description line, you "Pause, Test (which runs the piston) and view.
All I do is open WC, not through logging on to HE, just a browser bookmark or a link to WC on my mobile/tablet, scroll to my piston and then click test.
Couldn't be easier.
1 Like
