Skip navigation
Spot_konnan
Currently Being Moderated

InvokeEvent.reason always "standard"

Sep 22, 2010 4:23 AM

I test it on Vista. The air application is set as startup - checked. After restart or log in, application start and InvokeEvent.reason is "standard". What can I do. And I don't think that the problem is sdk version. SDK that I use provide me with class InvokeEventReason which has constant LOGIN. For those who will ask me about the SDK version enyway, it is flex_sdk_3.5.0.12683.

 
Replies
  • Currently Being Moderated
    Sep 22, 2010 10:36 AM   in reply to Spot_konnan

    What is the AIR SDK version number?

    You can execute:

    adt -version

    to get it.

     

    -ted

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 23, 2010 1:40 PM   in reply to Spot_konnan

    This version should not have the problem.

    Do you update the Runtime?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 14, 2011 6:43 AM   in reply to Spot_konnan

    I'm experencing the same thing. Was there any resolution to this issue?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 2, 2013 2:28 PM   in reply to phipwell

    Not the same thing, but also wrong, is the folowing behavior (tested on Windows 7 and SDK 3.5.0.1060): on first launch, the value of InvokeEvent.reason is LOGIN, as it should.

     

    If, however, I shutdown my AIR application, and start it again, manually, the value of InvokeEvent.reason is still LOGIN, while it should really be STANDARD.

     

    Hasn't anyone tested such a simple workflow? Good God...

     

    So, what could I do?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 2, 2013 2:43 PM   in reply to Claudius Tiberiu Iacob

    OK, I'm back with more on that issue: it only occurs when user logs off / logs on in place of restarting.

     

    So, If I log off, and then log on, the InvokeEvent.reason will remain set to LOGIN for the rest of the Windows session. If, however, I restart the machine, and then logon, the InvokeEvent.reason property will behave as expected.

     

    While I do agree that this is partially working, is stil not good enough for me...

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points