MrKim Well-Known Member Licensed User Longtime User Oct 17, 2013 #1 Not really a big issue but an FYI. My code compiled with the legacy debugger would run without the debugger. It would say waiting for debugger and then open. Code compiled with the rapid debugger will not run without the debugger connected. It says waiting for debugger and then closes. I don't want to sound like I'm unhappy. The new debugger is AWESOME! It will save me an ENORMOUS amount of time!
Not really a big issue but an FYI. My code compiled with the legacy debugger would run without the debugger. It would say waiting for debugger and then open. Code compiled with the rapid debugger will not run without the debugger connected. It says waiting for debugger and then closes. I don't want to sound like I'm unhappy. The new debugger is AWESOME! It will save me an ENORMOUS amount of time!
Erel B4X founder Staff member Licensed User Longtime User Oct 18, 2013 #2 The rapid debugger is made of two components: the device shell app and the desktop engine process. It cannot run without the desktop engine. There is no "user" code in the shell app.
The rapid debugger is made of two components: the device shell app and the desktop engine process. It cannot run without the desktop engine. There is no "user" code in the shell app.