Re: flex/air does not resize app when "call in use" statusbar showing on iphone

2015-03-10 Thread kevin.godell
I wish it was just my app, but alas, I created a new app and had the same results: http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" applicationDPI="160" backgroundColor="0x00">

Re: flex/air does not resize app when "call in use" statusbar showing on iphone

2015-03-10 Thread OmPrakash Muppirala
I am wondering if the application ever receives a resize even when the resize happens. Can you attach an event listener and see if that works? If it does, we can hopefully fix this within your app. If not, I am afraid it is either an Adobe AIR bug or a bug with the iOS itself. Perhaps reaching o

Re: [DISCUSSION] MXML pseudo states suggestion

2015-03-10 Thread Alex Harui
Hi Judah, I think your example from a few posts ago didn’t actually have a state-dependent attribute. Maybe try something like this: I think there might be too many backward-compatibility risks with changing the API signature of setStyle. The compiler could certainly generate a call to

Re: [DISCUSSION] MXML pseudo states suggestion

2015-03-10 Thread jude
The TL;DR was what if we treat inline pseudo states MXML like it is an inline style or like we treat CSS pseudo style declarations? When we encounter an attribute formatted like so, icon#up="myUpIcon.png" we, meaning the compiler, write out: temp.setStyle("icon", "myUpIcon.png", "up", true); // cr

Re: [14/14] git commit: [flex-sdk] [refs/heads/develop] - FLEX-34119 Running the over 10, 000 parameterized tests in the ant test runner takes over an hour! (On my computer it only takes a bit above t

2015-03-10 Thread Mihai Chira
Should I un-ignore this test, to see if it's faster on the server? (On my machine, in IntelliJ it finishes in three minutes.) I guess it's so slow because it's writing the reports to disk while running? Also, now that it's ignored, FlexUnit (Flash, really) throws a stack overflow error at around 1

Re: [DISCUSSION] MXML pseudo states suggestion

2015-03-10 Thread Alex Harui
Maybe, but the way the code currently works is that the states are declared in an MXML document and all state-dependent data is generated for that same document. While that state-dependent code does set styles and properties on other instances declared in that document, some of those instances are

Re: [2/3] git commit: [flex-sdk] [refs/heads/develop] - FLEX-34625 CAUSE: When focusThickness is set to 0, the BitmapData that HighlightBitmapCaptureSkin.updateDisplayList() tries to create is of 0 wi

2015-03-10 Thread Mihai Chira
I had a bit of time today to check this out again. It seems that UIImpersonator.testDisplay is just a Sprite, which means that the test runner is compiled with CONFIG::useFlexClasses set to false (see org/fluint/uiImpersonation/VisualTestEnvironmentBuilder.as). Does someone know how we can recompi

RE: [DISCUSSION] MXML pseudo states suggestion

2015-03-10 Thread Kessler CTR Mark J
Is this something that could be accomplished by overriding the stateChanged[1] protected method since it's used for setting styles when the state changes? [1] http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/core/UIComponent.html#stateChanged() -Mark

Re: [DISCUSSION] MXML pseudo states suggestion

2015-03-10 Thread Alex Harui
Hi Judah, I didn’t read your entire post. I think you missed some of the generated code for the state-dependent properties and styles. Take a look at how the assignment for a state-dependent style attribute looks and consider whether it would change your mind about what you want to do. -Alex O