HC3 QuickApps coding - tips and tricks
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
@cag014 (quick and dirty) refresh states "dumper" using http client instead of api.get. You've been around here for a while so you probably know api.get urls get translated to http://127.0.0.1:11111/api but for other forum members that may not be obvious.
IMHO this stays responsive and avoids blocking issues. Would require a bit more error handling for production because in rare case you might get an error from that call. The request never leaves the HC3 so it is quite stable, but li
