mooter

I have this device that I'm about to release, and skinned most of it, first as a test to see how much time and effort it takes to skin it, but even though it's functional, it's kind of funky and bleh. Now even though I'd still like to incorporate some custom ui elements into some devices, I'd like to adhere moderately to ui guidelines, but the biggest reason is that I want the UI to go with whatever skin the user is using, so live.colors needs a comfortable residency in my arsenal.

So, my experienced artisans, how do you go about sending live.colors values to your objects?

The 2 main avenues I'm think are [send] ie [s ---ui.???]

I'm still just acquainted with the Pattrs's. I thought I needed autopattr to keep all my settings for when the set reloads but I took it out and it didn't seem to make much of a difference. That's another issue though. Anyway, they're both employing some remote distribution, though maybe less so with Pattr.

I have this device that I'm about to release, and skinned most of it, first as a test to see how much time and effort it takes to skin it, but even though it's functional, it's kind of funky and bleh.  Now even though I'd still like to incorporate some custom ui elements into some devices, I'd like to adhere moderately to ui guidelines, but the biggest reason is that I want the UI to go with whatever skin the user is using, so live.colors needs a comfortable residency in my arsenal.

I'm still just acquainted with the Pattrs's.  I thought I needed autopattr to keep all my settings for when the set reloads but I took it out and it didn't seem to make much of a difference.  That's another issue though.  Anyway, they're both employing some remote distribution, though maybe less so with Pattr.

live.color - methods of distribution