Chigabooga -- the XDK builds standard Cordova (aka PhoneGap) apps. It has no bearing on the way your apps are initialized, how they run or how the various Cordova plugins work. Thus, there is no "fix" that the XDK can provide to deal with the audio delay issue you are experiencing. I recommend you search Stack Overflow for issues related to Cordova or PhoneGap apps and audio delays, and include keywords in your search regarding the plugin or HTML5 technique you are using to play your audio. Any solutions you find for Cordova/PhoneGap apps can be applied to an app built with the XDK, since it simply builds a Cordova app.

Ashley and — -- I've tried to summarize how best to update an existing Intel XDK project using the "new" Construct2 export option, here > https://software.intel.com/en-us/forums ... pic/607195 <

Ashley -- I'm not clear on how to refer to your "new" export process. Please read over what I have written to confirm that I have not left anything out and there is no confusion.

— -- you could use links to do what you are trying to do.

For example:

• export initial project (first time export)
• open initial project in the XDK
• export second time to a new location (preserving state of first export)
• replace www in first project (the active XDK project) with a link to the second project's www folder
• make subsequent exports to the second project

Now all subsequent updates from C2 go to the second location and only the www folder in your initial XDK project will be updated, leaving the <project-name>.xdk unchanged each time you export to the second project.

In this case your first project is the master XDK project, meaning it contains the plugins folder, the <project-name>.xdk file, etc. The second project is the master source code project, because it contains the www folder with all resources. This will work best with hard links, not soft links, which require that both projects exist on the same filesystem. Hard links are supported on Mac, Linux and Windows machines, so this solution applies regardless of the OS on your development system.

xmnboy - if the problem is the .xdk file being overwritten, perhaps a simpler workaround is to export to a separate folder, then copy all the files over apart from the .xdk file? i.e. just update all the asset files and leave the same project file.

Ashley -- that is the approach that should be taken: 1) export new project once then 2) export to a new location and copy updated files to the original project. This is a bit cumbersome and might be difficult for some developers to use or understand.

I'm thinking an approach that allows one to export only the www folder (call it an "update export") for delta updates. Perhaps if you detected an existing <project-name>.xdk file you automatically just update the www folder in the destination? I can show you how to detect if that <project-name>.xdk file has been processed and is now in use by the XDK.

— -- The pathnames in your video are blurry, so I cannot be sure, but I believe you exported the Construct2 project a second time, on top of an existing project that had previously been imported by the XDK. Is that correct?

If my assumption is correct, then I believe what is happening is you are confusing the XDK by changing the contents of a "known good" project file (the <project-name>.xdk file) with a project file that was exported by Construct2.

Try this process, instead, when you intend to export a new copy of your project from Construct2:

* "remove" the old project from the XDK project list * exit the XDK * delete (or rename) the old project's folder * export your Construct2 project * "open" the newly exported Contruct2 project

The <project-name>.xdk file that is exported by Construct2 is a "partial" project file, it gets "completed" by the XDK on the very first open. Once it has been added to the list of projects in the project file list it is expected to be in this "completed" state the next time it is opened -- but if that <project-name>.xdk file has been over written, the project is no longer in that "completed" state. This is likely the cause of the error message you are seeing in the video.

Let me know if the process described above works.

In essence, if you are going to export the same project, multiple times, onto the same location on your development system, you need to first remove the old project from the XDK project list AND remove it from your system (or rename the project folder so it is effectively gone).

Xam CDogs1964 PixelPower frazermerrick — -- please see the second half of the top post for a possible solution to the black screen problem on iOS 10 > https://software.intel.com/en-us/forums ... pic/685395 <

Please see second part of the top post for possible solution to the black screen problem on iOS 10 > https://software.intel.com/en-us/forums ... pic/685395 <

chrisnewman Guinness CDogs1964 -- please see second part of the top post for possible solution to the black screen problem on iOS 10 > https://software.intel.com/en-us/forums ... pic/685395 <

Give this a try > http://stackoverflow.com/questions/3841 ... os-10-beta < -- I've searched various forums, including the Cordova project, and am not finding anything specific, other than the link that I just gave you which recommends an update to the CSP tag in your index.html file. Also, this response on the PhoneGap Build forum > https://forums.adobe.com/message/8985487#8985487 < from "kerrishotts" has some useful info.

Give this a try > http://stackoverflow.com/questions/3841 ... os-10-beta < -- I've searched various forums, including the Cordova project, and am not finding anything specific, other than the link that I just gave you which recommends an update to the CSP tag in your index.html file. Also, this response on the PhoneGap Build forum > https://forums.adobe.com/message/8985487#8985487 < from "kerrishotts" has some useful info.

Give this a try > http://stackoverflow.com/questions/3841 ... os-10-beta < -- I've searched various forums, including the Cordova project, and am not finding anything specific, other than the link that I just gave you which recommends an update to the CSP tag in your index.html file. Also, this response on the PhoneGap Build forum > https://forums.adobe.com/message/8985487#8985487 < from "kerrishotts" has some useful info.

razinar -- I do not know how a C2 app works or how it handles Cordova plugins, internally, so I can only speculate...

[quote:bgrrxexb]Hi guys, i'm using the newest version of C2 and Intel XDK.

While exporting for Cordova i check the "Hide status bar" box.

In XDK build setting i check "Fullscreen" box.

The status bar is not showing while my app is running, which is what i needed.

However if the screen timeout or the user lock it, when restoring focus on my app the status bar is visible again and won't go away. Problem occours on Samsung Galaxy S5 with Chrome as browser.

I tried to import the Cordova Status Bar plugin in XDK, and added this action in c2:

Browser - on resumed - Execute javascript "StatusBar.hide();"

• I suspect the Cordova export "Hide status bar" does nothing for the XDK part of that export, we do not read the config.xml file, we read the <project-name>.xdk, assuming you used the "open an Intel XDK project" to import that Construct2 project.

• Thus, the "check fullscreen" in the Build Settings is what is causing your app to go to full screen mode.

• Calling "StatusBar.hide()" upon resume should do the trick, but you do need to make sure that plugin is part of your app. In the XDK, check the Plugin Manager to see if that plugin is part of your app. Full docs for that plugin are here > https://github.com/apache/cordova-plugin-statusbar <

• The config.xml preferences mentioned on that doc page can be added to your intelxdk.config.additions.xml file.

Like I said, I'm speculating, because I don't have detailed knowledge regarding how a C2 app runs internally.