Ah! Just what I needed. Works like a charm. Thanks. On Fri, Oct 31, 2008 at 12:19 PM, Alex Harui <[EMAIL PROTECTED]> wrote:
> Most containers have no backgrounds so the mouse falls through to what > is below it. Set a background on the container(s) > > > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > Behalf Of *Richard Rodseth > *Sent:* Friday, October 31, 2008 11:34 AM > *To:* flexcoders@yahoogroups.com > *Subject:* Re: [flexcoders] rollOut event > > > > Target is the pod (the window-like thingy) and related object is the > application. > > The pod is based on VBox and the title is currently an HBox with link > buttons and a spacer. As a test, I gave the HBox title a fixed height, and > the leavePod handler fires when moving off the info LinkButton in any > direction (i.e. into the HBox gaps/padding). > > Any way to avoid that? > > > On Thu, Oct 30, 2008 at 8:02 PM, Alex Harui <[EMAIL PROTECTED]> wrote: > > Examine the event's target and relatedObject properties to see where it > thinks it is going > > > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > Behalf Of *Richard Rodseth > *Sent:* Thursday, October 30, 2008 12:12 PM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] rollOut event > > > > I have a window-like MXML component with a title bar (currently done with > VBoxes and HBoxes) and a content area (a Canvas). Rolling over an info icon > in the tile bar causes another component to be overlaid (made visible) in > the content area. > > I used rollOver on the info button to make the overlay visible, and I added > a rollOut on the root (window-like) component and on the overlay itself to > hide the overlay. The puzzling thing is that the root-level rollOut fires > when I move the cursor out of the info icon to the right (remaining within > the title bar), but not when I move down towards the content area and > overlay (even with a gap between the title bar and overlay top). This is > actually not a terrible thing, user-experience-wise, but it's not what I > expected. Any ideas what's going on? > > Thanks. > > > > >
