A thread to share some coding techniques for QuickApps?
Because QAs are "long running scenes" (they don't have to be loaded and restarted for every event) - it is actually worthwhile to build up a library of "nice to have" code and include them in QAs.
Please login or register to see this link.
Please login or register to see this link. s
Please login or register to see this link.
Please login or register to see this link. client
List of posts:
Introduction to the QuickApp ana
File: Please login or register to see this attachment. v0.23
Some documentation on the basic toolbox < Please login or register to see this link. >
I have started to assemble a toolbox of "QuickApp" functions that are missing or "good to have". Based on my best practices so far - or functions that I'm "missing". I'm using it as a baseline for the QAs I'm currently coding.
Backward compatible with existing functions but add easy handling of children, easy scheduling of timers, formatti