[
https://issues.apache.org/jira/browse/FLEX-33742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770936#comment-13770936
]
Maurice Amsellem edited comment on FLEX-33742 at 9/18/13 4:33 PM:
------------------------------------------------------------------
If it's not possible to determine that the mouse event occurs inside another
Callout, then maybe the developper could manually indicate which nested
callouts should be ignored.
this could be done using DropDownController.hitAreaAdditions property.
However, it's not currently public.
So maybe adding a new *hitAdditionProperties* public property to *Callout* to
make that possible.
What do you think ?
was (Author: maurice.amsellem):
If it's not possible to determine that the mouse event occurs inside
another Callout, then maybe the developper could manually indicate which nested
callouts should be ignored.
this could be done using DropDownController.hitAreaAdditions property.
However, it's not currently public.
So maybe adding a hitAdditionProperties public property to Callout to make that
possible.
What do you think ?
> CalloutButtons inside another CalloutButton or Callout opened contents
> closeDropDown calls close the parent callout content
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: FLEX-33742
> URL: https://issues.apache.org/jira/browse/FLEX-33742
> Project: Apache Flex
> Issue Type: Bug
> Components: Mobile: Callout / CalloutButton
> Affects Versions: Apache Flex 4.10.0
> Environment: Windows
> Reporter: Carlos Velasco Blanco
> Priority: Minor
>
> When using a callout button inside the callout content of a different callout
> button I am having an undesired effect.
> Calling the dropdown method of the child callout button (the one placed at
> the callout content) is closing its callout content (as desired) but also
> closing the parents callout content.
> CalloutButton instances are to be closed using the closeDropDown() method
> which is causing the problem. Calling it for one instance is closing all
> instances. I think it was programmed that way thinking there would never be 2
> CalloutButton instances opened at a time, but It really happens when you use
> CalloutButtons inside the contents that are displayed when an instance of
> CalloutButton is opened.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
