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
Sure, I leave that up to you, I only slapped on a "local" to flag where so you could "diff" and decide "appropriate or not"
Thinking out loud... Maybe one "local" table to put all your private functions and variables and one global "hc3_emulator" table with everything you want to expose?
That would simplify checks I run in my "check global leakage script" that I run before loading everything else. Forgot to upload the code, here it is.
1614c1c4fbc1b6d40a997ecd9e46