Alex,
Is there a way to keep the app from being idle when in the background?
When do you anticipate a fix for this?
Thanks!
-Jake
On Thu, Apr 5, 2012 at 6:08 PM, Alex Harui aha...@adobe.com wrote:
**
Sounds like a bug in the idle management in AIR. They’ve been trying
different things
Well, we don’t have confirmation that there is a bug in idle management. But
if that was the cause, I don’t think there is a way to keep yourself from
becoming “idle”. I’m just recalling the kinds of issues that came up when they
started idle management a few years back. Google “Adobe AIR
So, any suggestions on a possible workaround to try? Currently, we have
the clients reverted back to AIR 3.1 and it's working fine but they have to
constantly deny the update. I'm considering bundling the app w/ AIR 3.1
using that Captive Runtime but I really don't want to do that either.
Did you try keeping some sort of screen updating going all of the time?
Current time, a news feed, something like that?
On 4/9/12 9:52 AM, Jake Churchill reyna...@gmail.com wrote:
So, any suggestions on a possible workaround to try? Currently, we have the
clients reverted back to AIR
We have up to 30 small modules that are getting loaded at startup and notice
that the accumulative perceived loading effect is slow when creating the
modules via...
_module.factory.create() as IVisualElement;
... as all of the modules are competing for CPU to draw themselves.
So, is there a
Yes, based on one of the posts I saw, adding a small image to the display
list once in a while. I basically did this every time data was received
over the socket (and removed it as well) and still froze the same.
Maybe I'll try keeping some kind of data related ticker or something.
Thanks!
Don’t call factory.create() until the first time you go to that tab.
On 4/9/12 11:16 AM, jamesfin james.alan.finni...@gmail.com wrote:
We have up to 30 small modules that are getting loaded at startup and notice
that the accumulative perceived loading effect is slow when creating the
Thanks Alex! We were hoping for that elusive disableNow function to add to
the invalidateNow(), validateNow() family. ;)
--- In flexcoders@yahoogroups.com, Alex Harui aharui@... wrote:
Don't call factory.create() until the first time you go to that tab.
On 4/9/12 11:16 AM, jamesfin
Flex SDK v3.6
Okay, I have a module that is called from an application. That module calls
another module. Trying to run any RemoteObjects from the nested module is
failing, resulting in the following error:
TypeError: Error #1034: Type Coercion failed: cannot convert Object@d3dcad9 to
9 matches
Mail list logo
