![]() ![]() Does this include all Adobe AIR Desktop Apps to run on the latest MacOS? I've received this email for Mac OS Applications. so I was wondering is there a way to manually give the InputDispatcher a focus, something like () However this makes the code a bit ugly and produces another source of error for asynchronous inapp events like a disconnect from our server while the initialization is happening, etc. I can avoid the error by splitting my code into chunks that I execute with delay, so that the InputDispatcher receives some love from the CPU in between. It looks like the reason is that the Android InputDispatcher has been frozen for too long and believes the application is unresponsive. events=0x9Į/InputDispatcher(2349): channel ~ Channel is unrecoverably broken and will be disposed! W/InputDispatcher(2349): channel ~ Consumer closed input channel or an error occurred. The related log entry in the Android LogCat I believe is the following: What happens is a cleanup of the lobby, followed by a creation of a high resolution Bitmap which is then used to create a texture in Starling. ![]() We have a reproducible crash on the Samsung Galaxy S3 with a script that takes some seconds to execute. ![]() Im developing on Windows 7 64bit machine. Just to add, when I run my built application, I take a look at the running app in my task manager to see if its 32 or 64bit and every time I run my built app its showing the *32 by the app name. The ADT compiler through an error stating it did not recognise this new descriptor.Īny help what so ever with this would be very much appreciated. I want to specify a 64bit build version and so far Ive found a new application descriptor 64. This would allow me to test it first to see if there were any problems.īut the only thing I've found with instructions is:Ĭombined Windows 32-bit and 64-bit AIR SDK | Adobe Developer ConnectionĪnd the problem is Im using the SDK's ADT app to package the runtime from that SDK, with my application. So Ive downloaded the most recent Adobe Air SDK 29 and Ive tried researching how to build a Captive 64bit version of my software, but with very few results.īefore I build of IOS I wanted to build a 64bit version for windows. Ive successfully created many 32bit applications but with the recent decisions by Apple to encourage developers to only build 64bit versions of their software, if they want it in the Apple store. If you'd like to provide additional input, please take a minute and take this three question survey so we can better understand what folks would like to see in future releases. We wanted to get your feedback on some of the items outlined by the community. We've also been following a feature request thread on the Starling forums. Support for the latest SDK on iOS 11 and Android O.Improved monitor and resolution settings for AIR Desktop.Support for 64-bit AIR – Windows Captive Only. ![]() As always, this list may change as we receive feedback from the community. We hope to have our official Flash Runtime roadmap updated soon, but until then I wanted to share some of the features we'd like to accomplish in our upcoming releases. Many of you have asked for a roadmap update. Adobe remains committed to AIR and we believe it continues to be a great desktop and mobile development platform. Let me start by saying that today's announcement was not about AIR, and instead focuses entirely on Flash Player and the browser plugin environment. With the news today regarding Flash Player, I'm sure many of you have questions regarding AIR and its future roadmap. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |