[flexcoders] Re: Working with nested Buttons

[Todd]

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 flexcoders@yahoogroups.com, 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.

Re: [flexcoders] Re: Working with nested Buttons

[Josh McDonald]

I *have* to know - what kind of evil requires a button that contains other
buttons?

;-)

-Josh

On Wed, Jan 7, 2009 at 1:37 AM, Todd tpreka...@gmail.com wrote:

 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 flexcoders@yahoogroups.com, 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.
 



 

 --
 Flexcoders Mailing List
 FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
 Alternative FAQ location:
 https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847
 Search Archives:
 http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups
 Links






-- 
Therefore, send not to know For whom the bell tolls. It tolls for thee.

Like the cut of my jib? Check out my Flex blog!

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: j...@gfunk007.com
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk