I solved my problem. On the nested-child button, all I had to do was set buttonMode="true" and useHandCursor="true". It wasn't enough to just have the LinkButton and assume that it would behave as a button.
All works perfectly now with my complex button skin. --- In [email protected], "Todd" <tpreka...@...> wrote: > > Hello, > I have a custom Button control that uses extensive skinning (done in > Flash, and linked through the Button's skin-style) to change the skins > for mouse over, down,etc. The custom Button can contain multiple > child objects, like other LinkButtons. > I can't get the sub-button to trigger, though. On the parent > button, I've fiddled with buttonMode and mouseChildren properties. > So, I tried making the Parent a VBox (or any type of container) > instead of a Button. Doing this enables me to now get the child > buttons to trigger properly. However, I've lost the button skinning > for mouse Over, down, disabled, click, etc... The skin is a > programatic skin that has implementations for downSkin, > selectedOverSkin, overSkin, selectedUpSkin, etc... > > What would be the preferred way to get the HBox (or any container) > to act like a button with custom button skinning, and at the same time > be able to have nested buttons that would take priority when the mouse > hovers over them? I'd like to think I'm missing something trivial in > getting this to work because it seems like a pretty common use case. > > Thanks for any suggestions. >
