it seems to me that there is perhaps a slight buggette with buttons or maybe its the user approach? no its deffo a bug
it seems custom buttons dont use same functionality as the cbuttons as these behave as you'd expect?
I did some experimenting
when adding a custom button I've added the over & down states appropriately however the change event doesnt always take place on a mouse click where you would expect the down state to be triggered every time
my findings
-button with just normal layer, action being on normal layer
* on clicking button it always triggers the change event, which you'd expect, fair enough but this does not necessarily add to the overal aesthetics of the over, down states which are desirable in a button/style
-button with normal, down, action being on normal layer as above
* on clicking it always triggers the change event as above, however when you the click and hold the button down then release it does not trigger the change event
-button with over, normal, down, action being on normal layer
*never triggers the change event as over & down states only being used, unfortunately the passthrough does not work on over image which i thought it might as to avoid masking the normal button
-same as above but action on the down image
* clicking doesnt necessarily trigger change event but down action does
adding an id to the normal button does help a little but is still prone to mostly clicks not processing the change event
to me most users seem to click buttons and expect the event or something to change, this works ok if the custom button has no over, down effects but then does not have the nice aesthetics to go along with the transitions you'd expect a button to have
I was hoping passthrough might have saved it and made a difference but it has no effect except if added to over then normal is never hit
hopefully you can look into this Cliff,
thanks
Kev