Sorry for my misinformation, My actual scenario is based of these news pull-requests: https://github.com/apache/flex/pull/19 https://github.com/apache/flex/pull/20 https://github.com/apache/flex/pull/21
I did activate the MX FTE Text compiler option in order to get the new font family in mx components, now all components adopt the new OpenSans font as you can see in baseline pull-request (21). I did cancel the old pull-request 8,9,17 in favour of these: https://github.com/apache/flex/pull/19.patch https://github.com/apache/flex/pull/20.patch The pull-request 21 exist only to share with you my new baseline image cuts, and the differences each other. If this scenario seems OK, I will repair the new AssertPixelValues fails. Thanks, -Jose. On Aug 29, 2012, at 9:26 PM, Peter Ent <p...@adobe.com> wrote: > I have not applied Jose's patches. I did find the warnings in the log > files, though. I have just modified the code and I want to see what > happens. > --peter > > On 8/29/12 3:23 PM, "Alex Harui" <aha...@adobe.com> wrote: > >> >> >> On 8/29/12 12:03 PM, "Peter Ent" <p...@adobe.com> wrote: >> >>> I got no warnings in the output, just bitmap compare failures. I'm going >>> to run it again to be certain, though. >>> >> I don't see the EmbeddedFontRegistry warnings in the output of the test >> engine. It might be in the log file. But I definitely see it in the >> debugger when debugging and it definitely made a difference in one folder. >> >> BTW, did you apply Jose's patches? (8, 9, 17). I'm going to put down what >> I'm doing and run the mx folder again. >> >> Save your list of tests passed and failed and email it or post it. I'll >> compare when the run finishes. >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >
