Ok, thanks. That clarified some things for me, and now I've now gotten it to work by fixing code that filled in the shape between the lines only.
Thanks. --- In [email protected], Alex Harui <aha...@...> wrote: > > If your programattic skin doesn't have any pixels in some area, the mouse shouldn't detect it. The mouse sees transparent pixels as valid target area. > > From: [email protected] [mailto:[email protected]] On Behalf Of Todd > Sent: Thursday, December 18, 2008 8:48 AM > To: [email protected] > Subject: [flexcoders] Re: Button hotspot for skins that aren't rectangular borders > > > Hmmm...the formatting previewed correctly, but was totally messed up > during the actual post, let me try again: > > |-----\ eol > | \ eol > | \ eol > | / eol > | / eol > |-----/ eol > > --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, "Todd" <tprekaski@> wrote: > > > > Hello All, > > I have a button with a skin that isn't a rectangular border. What's > > the best way to have the button only change states when the user > > mouses over the perceived button bounds (with an irregular skin). > > > > For example, I have a button and custom skin that looks like: > > > > |-----\ > > | \ > > | \ > > | / > > | / > > |-----/ > > > > Notice the right-side, and how there's an angular triangle. I'd like > > the button to NOT change state when the mouse isn't intercepting with > > what the user actually sees as a button. > > > > BTW, I'm using a programmatic skin. I tried just using button states > > with different PNG images that have the background transparent outside > > the perceived border, thinking that Flex would manage the hotspot > > automatically for transparent pixels. > > > > Any input would be appreciated. > > > > Thanks. > > >
