I am using B4A 9.01.2
When working in Rapid Debug mode, I often need to modify a layout of an Activity. Since the modification is not in a module, I can't do a Crtl+S to recompile the app in real-time and see the layout changes.
So, I thought I could simply click the "Restart (F11)" button to recompile and show my layout changes quickly. But when I do, there is a pause when it tries to run again and then I get the error "Rapid debugger failed to connect to device".
However, if I instead click the Stop button and then *immediately* the Run button, the app restarts very quickly and my layout changes are displayed. This is a reproducible bug.
Why does the Restart button fail, but a stop and run work?
When working in Rapid Debug mode, I often need to modify a layout of an Activity. Since the modification is not in a module, I can't do a Crtl+S to recompile the app in real-time and see the layout changes.
So, I thought I could simply click the "Restart (F11)" button to recompile and show my layout changes quickly. But when I do, there is a pause when it tries to run again and then I get the error "Rapid debugger failed to connect to device".
However, if I instead click the Stop button and then *immediately* the Run button, the app restarts very quickly and my layout changes are displayed. This is a reproducible bug.
Why does the Restart button fail, but a stop and run work?
