Just wanted to update this with a solution in case anyone else in the future is going down the wrong road like I was. I found out about RollOut/RollOver events shortly after I posted this. Found an example of that in the FlexStore sample application on Adobe's site. So I switched to RollOut/RollOver. This fixed the issue with the accordion header, but created strange flickering where the events were firing as I moved around my container.
The solution was here http://tech.groups.yahoo.com/group/flexcoders/message/88339 I think this is very un-intuitive and should be documented somewhere in the docs, the part about a container not having a background and that's what was triggering the RollOut/Over events. --- In flexcoders@yahoogroups.com, "Brian" <[EMAIL PROTECTED]> wrote: > > Reposting from a couple days ago, trying to ask the question better, > hope that's ok... > > I've got an accordion component with VBoxes as the children. The > VBoxes contain several custom components each, enough that I've got > scroll bars on the accordion children VBoxes. The custom components > have states that are supposed to be triggered on MouseOver and > MouseOut. I use getBounds on these components to see if they contain > the MouseOut event's point. If it doesn't, then I revert back to the > original state. The MouseOver state adds a couple buttons at the > bottom of the component. > > Everything is working fine, except for when the lowest visible > component in one VBox is clipped by the header of the next accordion's > child. When I move the mouse from inside the component, down out the > bottom and over the next accordion header, the coordinates of the > MouseOut event still fall within the local and content coordinate > system of the component, even though it is clipped on the bottom by > the header. > > I've read through the coordinate system docs and tried various > permutations of local, global, and content positioning. I would've > thought that the local coordinate system would reflect what is > visible, but it isn't acting like that is the case. > > Any ideas on how I can detect MouseOut on that component that is > clipped by the next accordion header? > > I may have to try different layouts, like a ViewStack with a TabBar >
