flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maurice Amsellem (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-24623) Remove private declarations in PopUpAnchor
Date Sat, 14 Dec 2013 21:05:08 GMT

    [ https://issues.apache.org/jira/browse/FLEX-24623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848452#comment-13848452

Maurice Amsellem commented on FLEX-24623:

However, after thinking about it again, since it's mx_internal, we cannot guarantee that a
third party code does not call it and if you change to protected, that would break this code.
As a general rule, you can only increase the accessiblity of a variable, not decrease it.
Accessibility order is the following :
private < protected < internal < {custom_namespace, such as mx_internal} < public.

> Remove private declarations in PopUpAnchor
> ------------------------------------------
>                 Key: FLEX-24623
>                 URL: https://issues.apache.org/jira/browse/FLEX-24623
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Spark: PopUpAnchor
>    Affects Versions: Adobe Flex SDK 4.1 (Release)
>         Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Other (specify version)
> Language Found: English
>            Reporter: Adobe JIRA
>            Assignee: Maurice Amsellem
>         Attachments: Fix_for_FLEX-24623.patch
> I'm trying to entend PopUpAnchor to add the ability to create modal popups with it (see
> Due to the plethora of private methods and variables I am unable to do this, and have
had to duplicate the entire class (which is still very common when trying to extend or change
the functionality of Adobes components).

This message was sent by Atlassian JIRA

View raw message