I am suffering with regular XDK V3088 freezes when switching to the Emulator tab. When I make a minor code change and go back to the emulator it will freeze around 20% to 30% of the time.
I have turned off the refresh function to stop crashes, but the freezes are equally as annoying.
I cannot do anything. Waiting does not resolve the issue. I have to force quit XDK (Mac El Capitan i7 with 8GB RAM) and restart. I am them prompted for a safe start or normal start.
Thanks for the information Nick. Unless this problem can be reproduced, it cannot be fixed. And I am trying to reproduce it. There have been some similar issues. Maybe some other user's steps will help reproduce the issue.
Nick -- try using the Debug tab as an alternative. If you switch to the Develop tab and make changes and then switch back to the Debug tab it will prompt you to reload the project. It's not as obvious as the Emulate tab, but it has the same effect. It also provides a much higher-fidelity debug environment.
Ok! I would recommend using twitter bootstrap. And for further details please see this FAQ: https://software.intel.com/en-us/xdk/faqs/app-designer#best-app-designer-framework
And they are in the order what we recommend.
I recommend you use an external editor to work on your source files (such as Sublime or Brackets) while you keep the Emulate tab open. This way you don't need to keep switching between tabs, which appears to be the thing that causes a freeze. Also, please update to the hotfix release of 3240. Using an external editor, rather than the built-in editor, is perfectly fine, the tool is designed to allow that. I do it all the time.
I am now using brackets to edit code however there are still some issues.
Crashes on refreshing after updating code outside of XDK.
The need to use designer and then switch back to Emulator can still cause a freeze.
Nick -- sorry, but we haven't identified any other workarounds. :-( It is a known problem and a high importance issue has been filed. We'll add to the sticky note regarding this problem if we find additional workarounds. The only other suggestion I have is to use the Debug tab rather than the Emulate tab. It will allow you to reload and restart the app when you make changes to your files. If you are not prompted by the Debug tab to reload changes sources you can force it by clicking the "bug" icon in the toolbar while you are debugging in the Debug tab, that will force a reload of your app's sources.