Programmatically determine the average greyscale

[Sannyasin Brahmanathaswami]

The buttons use a pattern so they are not transparent.

Yes, we are very familiar with the drop shadow technique also...

 Yes, we could use field + group methods, but I would prefer to keep is simple so that I can dynamically swap out the background patterns and, eventually, dynamically add and delete buttons  to the group. if we still with just the button template, then this keeps it simple.  200,200,200 seems to cover almost all cases so far.  A small JSON file with just the button names, links, and the ID of background patter  could be easily run on a repeat loop to instantiated the group of buttons after setting the btn template...  dynamically. Adding a field into that mix starts to get messy.

On the larger main card images/title I do have a field and I will  give the shadow a shot.




On February 20, 2016 at 5:57:30 PM, J. Landman Gay (jacque at hyperactivesw.com<mailto:jacque at hyperactivesw.com>) wrote:

Shadows work on button names/labels the same as they do for fields if
the button is transparent. The shadow affects only the text.