Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Were there any further developments on this bug report? I am having the same issues, only from what I see it's also on XP Service Pack 3, and haven't really found any solutions.
Copy link to clipboard
Copied
Hi All,
Any updates on this ? i am facing same issue in Windows XP SP3 but this issue is not coming Windows 7 and 8, windows Server, MAC OS.
Please let me know if you have solution of this issue
Copy link to clipboard
Copied
I found out an another way to trigger this bug that does not terminate program correctly. Here a way to reproduce the bug:
Start an AIR application, let it load.
Go to your taskbar on the bottom of the screen and find you AIR application there.
Right click on that AIR application
Click Close
Open up your task manager and go to Processes
After you closed it as mentioned above, your AIR program is actually still running in the process list even tho it got closed. It should have been terminated but it never did due this bug.
I tested this bug on Window XP service pack 2 and Window Vista Service Pack 1. Both are affected. I have not be able to test this on Mac OS X.
If you trigger this bug, your program wont be able to rerun again unless you reboot your computer or log off/log back in.
I have not report this bug yet.
No solution yet except tell the user not to right click -> close as mentioned above...
Copy link to clipboard
Copied
I can't reproduce this problem.
-ted
Copy link to clipboard
Copied
What operating system are you running? In Window Vista service pack 2, it
doesn’t reproduce the bug anymore... Maybe same for XP service pack 3...The
test was based on Ajax made applications.
Copy link to clipboard
Copied
I tried a SWF AIR app. on Vista.
I will take a look at a AJAX app.
Copy link to clipboard
Copied
Use the following code to close the application properly.
public function applicationExit():void
{
var exitingEvent:Event = new Event(Event.EXITING, false, true);
NativeApplication.nativeApplication.dispatchEvent(exitingEvent);
if (!exitingEvent.isDefaultPrevented()) {
NativeApplication.nativeApplication.exit();
}
}
call this funciton by using the close event in <mx:WindowedApplication close="applicationExit()">
More details about this can be found here: http://help.adobe.com/en_US/AIR/1.1/devappshtml/WS5b3ccc516d4fbf351e63e3d118676a5d46-8000.html
Copy link to clipboard
Copied
Hi there, i had such problem too and the code given by coolkams didnt work for me.
Here is what i did :
First thing i want to know the the main app is activated:
NativeApplication.nativeApplication.addEventListener(Event.ACTIVATE, onAppactivation);
Then the callback function add a CLOSE event listener to the current active window wich is the main application window:
private function onAppactivation(e:Event):void
{
NativeApplication.nativeApplication.removeEventListener(Event.ACTIVATE, onAppactivation);
NativeApplication.nativeApplication.activeWindow.addEventListener(Event.CLOSE, applicationExit);
}
Finnaly in the CLOSE event callback function :
private function applicationExit(e:Event):void
{
e.currentTarget.removeEventListener(Event.CLOSE, applicationExit);
NativeApplication.nativeApplication.exit();
}
That did the trick for me, hope it will help other people too...