Comments on: What is mx_internal ?

By: Random assortment of Flex tips « Hillel Coren

Random assortment of Flex tips « Hillel Coren — Sun, 07 Jun 2009 11:44:51 +0000

[...] more info… [...]

By: Toby Ho

Toby Ho — Wed, 25 Mar 2009 20:24:49 +0000

Nice! This info was just what I needed. Thanks.

By: amar shukla

amar shukla — Mon, 10 Nov 2008 13:12:04 +0000

i am a newbie in flex !
can you tell me what is the use of using it as its already default namespace inside flex ???
As i got to know about it that its just to define the scope as public/protected/internal …
so why to use this explicitely as mx_internal var xyz:string ;

instead we can use internal var xyz:string;
what is the need of using mx_internal ?
can you please explain it to me Raghu ?

By: Tom

Tom — Wed, 05 Nov 2008 14:26:22 +0000

I cant believe that we have to hack all the time the framework! Why they didn’t declare these fields as public?? For the videoplayer the smoothing is very important and every time you need to extends components to access protected or mx_internal fields.

Is there a performance issue between public/protected/mx_internal??

By: Paul D

Paul D — Tue, 18 Dec 2007 01:32:40 +0000

If “mx_internal” is for things that may change in future versions, how important is the “_parent” of UIComponent?

/**
* @private
* Reference to this component’s virtual parent container.
* “Virtual” means that this parent may not be the same
* as the one that the Player returns as the ‘parent’
* property of a DisplayObject.
* For example, if a Container has created a contentPane
* to improve scrolling performance,
* then its “children” are really its grandchildren
* and their “parent” is actually their grandparent,
* because we don’t want developers to be concerned with
* whether a contentPane exists or not.
*/
mx_internal var _parent:DisplayObjectContainer;

By: Mrinal Wadhwa

Mrinal Wadhwa — Tue, 04 Sep 2007 07:46:39 +0000

Raghu, A vary nice explanation.

Just to add the customary disclaimer … Adobe uses the mx_internal namespace to mark things that may change in future versions of the framework .. so you have to use it at your own risk … because your inherited class or component may not work with future releases of Flex