Thanks. I'll look up that tutorial.
I used to build custom screens and themes for high end universal remotes (before smart phones took the stage) so I'm pretty comfortable with trial and error and have a grasp of how theae kinds of things layer together. The thing that's killing me right is the lack of a SIMULATOR. (Or is there one I'm missing somehow?). Making changes to a theme, transferring back to escribe, uploading, and testing is too tedious. ..especially not knowing some of the most basic things like terminology and syntax.
Like, what the hell is a toggle? And why isn't there an easy way to find the source/target/structure for what screen a control is on or how its status changes. Having only one screen visible at a time sucks. Hrmm... I'll get it. I just wish there was at least a basic help file with definitions, list of functions, and such.