Thanks Alex, I was offline a few days. -Mark
-----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Sunday, May 12, 2013 2:15 AM To: dev@flex.apache.org Subject: Re: Mustella list tests failing Update: I didn't look into whether validateNow() is truly necessary or not, but in my analysis, it appears that the tests were relying on the list drawing at full alpha before the tween kicks in, which I think would run the risk of a "blink" and Mark's change seems to fix that, so I'm going to go and change the tests. On 5/11/13 9:00 AM, "Alex Harui" <aha...@adobe.com> wrote: > It was Mark's change for https://issues.apache.org/jira/browse/FLEX-23974 > > The validateNow() call he added changes the selectiontween timing somehow. > The bitmap captures the tween in action which is why the color isn't final. > > I'll look into it more this evening unless Mark gets to it first. The > answer may be to delay the compare bitmap, but first I want to see if a big > hammer like validateNow() on the entire list is truly required to fix the > bug. > > Hopefully Mark will now remember to run tests before checking in ;-) > > > On 5/10/13 10:55 PM, "Alex Harui" <aha...@adobe.com> wrote: > >> I'm looking into this over the weekend. >> >> >> On 5/1/13 4:27 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >> >>> Hi, >>> >>>> Well they are all Failed CompareBitmap right? So we just have to track >>>> down graphical changes? >>> >>> >>> The colour of a selected item seem lighter/more transparent, I had a quick >>> look through the changes and couldn't see anything obvious. I do know it not >>> the Bitmap changes or the 480 dpi changes I made the other week. >>> >>> Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
