Hi,
One easy way, and a way I really recommend to devs is;
protected function tabButtonFactory():IFactory
{
return navItemFactory;
}
Then in your subclasses always reference tabButtonFactory and your code
always has a hook to deal with changes made in the mx_internal namepace.
Works well, and I would advocate this approach as a seasoned component
developer.
Peace, Mike
On 6/6/07, rashmi_nraj <[EMAIL PROTECTED]> wrote:
Hi All,
I am facing an issue with TabBar. I have extended the TabBar so that
it uses a custom Tab created by me.
I am able to do it without any hassle by using the namespace mx_internal.
But I do not want to use it as the code might break in the future
releases of Flex. I need some suggestion regarding the usage of
mx_internal and how to design the components with out using this
namespace.
Can anyone from Adobe tell me how to deal with this namespace. How
severe will be the effect if I use mx_internal namespace?
Thanks
Rashmi
--
Teoti Graphix
http://www.teotigraphix.com
Blog - Flex2Components
http://www.flex2components.com
You can find more by solving the problem then by 'asking the question'.
