flex - Adobe AIR issue -


I have an Adobe Air app with a chart component displaying some online data chart components about 10 of them Have to display a bunch of parameters. There is a timer in the application to display the current system time.

The timer from the chart component (using a bindingable object) has been applied as shown below. A separate bindingable object is used to prevent delay in the timer.

  Private Function (Event: Timer Event) on OnTimerEvent: Updated time in zero {// screen; oCurrDate = new date (); Curitime = Odataformer.format (ocraduate) .stisting (); OCurrDate = null; // To update the chart about the update, Odd-Bindable Object // call every 250 ms oUpdate.bupdate =! OUpdate.bUpdate; }   

The Iam Chart's update event is shown below by using a callter function. UpdateParameter () will update the dataprovider of each parameter and it will draw.

  Function on public unchanged avenue (evt: PropertyChangeEvent): The first parameter on void {// aPlotIndex 0 is set to aPlotIndex.push;); This.callLater (Update Parameter, aPlotIndex); }   

The problem is that the timer and chart update stops after 20 to 21 days of running, after 20 or 21 days, the update is only on mouse move. When I showed the mouse time and amp; The data is updated in the chart.

I profiled the application and found that there is no memory leak problem. I am logging all the errors, but I did not find any errors in the log. Everything looks weird

  1. The caller is due to using the function.
  2. Is this timer still running, but the frame is not updating.

    I am using Flex SDK 3.3 and Flex AIR version 2.0.4.13090.

    Please guide me to solve this problem.

    Please read the documentation for timer .

    The total number set to run the timer, if the repeat count is set to 0, then the timer continues indefinitely, until up to 24.86 days , or when The stop () method does not apply or the program stops. If the repeat count is nozzle, the timer runs the specified number of times. If the repetitive account is set to a total that is equal or less then the current timer stops and will not fire again.

    Maximum one int , which uses the timer to store its current calculation int Maximum value of 2,147,483,647 is . is equal to 2147483647 / 24.86 days / 1440 minutes / 60 seconds / 1000 milliseconds 1 (giving or taking, the way the number is rounded according to the 'docs'), which aligns with this fact That the internal clock timer is gone.

    So you can not set the option to fix it. Instead, you can work around it, assuming that nothing really depends on the value of your timer. Every time a timer runs, call

      timer .set (); Timer.start ();   

    This will reset the timer to 0 and start it again, which means that your delay is not greater than that (24.86 days) Which may not be possible)

    In addition to this, I would like to say that the Flex and AR versions you run are critically old, both of which are approximately 5 years old at this point. Because of the new versions of AIR windows and OS X, it can run properly (and not on mobile anymore) if everything works, but it is always good to know (many posters do not know if their flex and How are Sky SDKs?)

  3. / li>

Comments

Popular posts from this blog

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -

Matlab transpose a table vector -

c# - Textbox not clickable but editable -