On 5/27/15, 1:11 AM, "Tom Chiverton" <t...@extravision.com> wrote: > >It seems happier overall now since you threatened it any way :-)
I know for sure there was at least one other time where, without any code changes, things started working again for a while. So I’ll bet we start seeing the failures again eventually. When things start failing, the indication is that, despite the fact the SWF asks for a 600 pixel height, the application ends up with 566 pixels in height. I’ve put some trace statements in CompareBitmap to try to show us whether the SWF itself didn’t get 600 pixels (which would indicate some player issue) or whether the application is the only thing at 566, which would point to our code somehow. I’m wondering if there is some player popup, status bar, additional menu bar, or something like that, that would deny the SWF its 600 pixels to show some message about updating or being launched from a service. Then when I go login and handle the player window from the user application level, it thinks I’ve ack’d something and doesn’t take away those 34 pixels. -Alex
