This content has been marked as final. Show 4 replies
Well, there's two ways to approach this: one is to extend the control rather than change the source code. The other is to compile your own framework SWC file from your new source and compile your apps against that new SWC file. There should be instructions on how to do this on the opensource site here:
Usually you just extend the Flex component either in AS or MXML, and place your overrides there.
See these FB3 help topics:
About custom components
Defining a method override
About creating advanced components
Creating MXML components visually
Yes, I have extended TabNavigator into a custom AS Class to create a workaround, but I am hoping to be a Contributor soon, and want to know how I can fix the bug in the source, so that I can test it and submit a patch when needed.
In that case you probably just copy the .as file to your Flex project, as well as any includes, etc.