by eValid » Fri Dec 05, 2008 4:18 pm
Flex can be daunting...
Evidently, and we are still researching this, if your Flex object is compiled with the automation interfaces in place it is possible in priciple to have full object mode access to all the internals.
But having the Flex object compiled with these libraries in place imposes a performance penalty and it appears that the majority of Flex objects that are deployed to the field do NOT have the automation access.
eValid can, however, deal with the no-automation-access version of a Flex object by using the internal Application Mode. While this is not as sophisticated as we all would want -- it does not have any more information that the name of the object and x,y locations of spots on its face -- at least it is reliable.
Also, it may be important to note that this Application Mode is seamlessly integrated with regular object mode test playbacks.
The eValid Support Team
