Hi Piotr, Maybe I'm not understanding the scenario. I assumed that the problem Justin is trying to fix is that you roll over a component, the component shows a tooltip, but the tooltip appears under the mouse so you get a rollout of the component and rollover the tooltip. The rollout of the component causes the tooltip to go away resulting in a rollover of the component which causes the component to show a tooltip, and so on.
If the tooltip cannot be a target for mouse events (mouseEnabled=false in Flash and I think it is "pointer-events:none" in JS) then I think the tooltip will not cause a rollout on the component when it appears under the mouse. One reason for tooltips to be in a bead is because there can be many different implementations. The one that currently exists is as simple as possible. There is no delay between rollover and showing the tooltip. There is no "scrubbing" support where you roll from one button to the next in a ButtonBar. It doesn't support interactive tooltips that do want to be mouse targets. There is no logic for smart positioning of the tooltip. All of these options will hopefully be implemented by volunteers in a PAYG fashion. Thanks, -Alex On 7/11/17, 8:01 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Alex, > >What do you mean by Mouse "transparent" ? We still need to use some event >mouse (enter/leave) where after roll over on the element tooltip should be >shown. > >Piotr > > > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FRe-2-5-git-commit-flex-asjs-refs-hea >ds-develop-FLEX-35338-stop-cursor-from-spinning-CPU-from-spiking-tp63061p6 >3099.html&data=02%7C01%7C%7C232a34024264401d485608d4c872f6df%7Cfa7b1b5a7b3 >4438794aed2c178decee1%7C0%7C0%7C636353843465345667&sdata=QC3t2Y3rI%2BVyBvA >KcjqwnoIilH5TLLkQ%2FBTODiQmEv4%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
