Andy, It answers his question and it does work.
If the label is present, you click on the label and the Button functions correctly. I don't know what he is aiming for here but, if you 'don't' have a border, there is no other hit area specified for the component. So, how are you going to get mouse events from a component that dosn't have a hit area? Bottom line is, this approach does work if you plan to use a label, other than this, why would you want a button without a label and border if you want to click on it? Peace, Mike On 11/29/06, Andrew Trice <[EMAIL PROTECTED]> wrote:
I'm not sure that approach really works… The buttons don't show up at all. -Andy _____________________________________ *Andrew Trice* Cynergy Systems, Inc. http://www.cynergysystems.com Blog: http://www.cynergysystems.com/blogs/page/andrewtrice Email: [EMAIL PROTECTED] Office: 866-CYNERGY ------------------------------ *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On Behalf Of *Michael Schmalle *Sent:* Wednesday, November 29, 2006 11:05 AM *To:* flexcoders@yahoogroups.com *Subject:* Re: [flexcoders] Styling in Flex is officially ridiculous Well, Before your loose it... try myButton.setStyle("upSkin", null); OR Button { upSkin:ClassReference("null"); } OR <mx:Button upSkin="{null}"/> Peace, Mike On 11/29/06, *ben.clinkinbeard* <[EMAIL PROTECTED]> wrote: OK. I am usually very hesitant to criticize Adobe because of the immense respect I have for their employees and the amazing technology they create. I have built my career around their products. That being said, the styling capabilities in Flex are downright silly. I have suffered silently through some small, yet extremely annoying "nuances", but this one takes the cake: You can't style a Button to not have a border!!! Developer: "Hey button, go ahead and skip your border drawing routine." Button: "Eff that! I love my borders and I ain't getting rid of them for anyone!" WTF. I can understand not supporting some styling features people would like, but not supporting one that is just turning something off? What gives? I realize I could probably subclass Button and override the drawing but that is uber-overkill for something that should be a simple attribute. If someone from Adobe can offer a valid reason for why this isn't supported I would love to hear it. I would also be very interested to know if styling is an area that is being focused on for significant upgrades in future versions. Thanks, Ben -- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
-- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
