I managed to get rid of the error by replacing the following line within the "invalidate" function:
Replacing the way the method is referenced from dot syntax to square brackets circumvents the strict compile mode.
However, as explained here close to the end of the article, this does not good coding practice.
The core problem here would seem to be the fact that the FlowGroupElement class is not declared as dynamic...
There is no FlowGroupElement.getChildAtIndex method.
There are these two:Returns the FlowElement child at the specified index.
FlowGroupElementSearches in children for the specified FlowElement object and returns its index position. FlowGroupElement
I think you meant getChildAt.
Hope that helps,
Yes, that did help. Thank you Rich.
It seems that the timoisalive version of the CSSFormatResolver class had a subtly different invalidate method than the original class found in the SimpleEditorWithCSS flex example.
I didn't actually modify the invalidate method in my version, Adobe's version refers to the getChildAtIndex method.
My version differs from Adobe's in the way that I am giving the resolver a StyleSheet object instead of having it use the Flex framework StyleManager class to resolve styles.
First of all thank you for making the CSSFormatResolver class independent of the Flex framework.
Secondly, I feel the need to rephrase my last sentence:
It seems that the timoisalive version of the CSSFormatResolver class had a subtly slightly different invalidate method than the original CSSFormatResolver class currently found in the SimpleEditorWithCSS flex example.
There has been a lot of cleanup and renaming of APIs we do review them constantly to try and make them be consistent and have a natural feel to AS3 developers. Please check the release notes when you pickup new textLayout.swc versions. We make every effort to log changes in the release notes. That said I'm sure there are omissions.
The most recent examples are posted here including an updated SimpleEditorWithCSS:
Apologies for the confusion and thanks for putting up with the API shifts. We really do appreciate your efforts and do want to support you. We're a tad short handed right now for various reasons - but that's all going to get fixed. Soon I hope!
I'm especially pleased folks are using the IFormatResolve interface - it wasn't a feature request internally I added it because I thought it would be cool. Really nice to see it getting leveraged.