I haven't tried that, but if seems like it should work actually.
On 12/26/17 12:14 PM, Mike Kerner via use-livecode wrote:
But can you just put the "breakpoint" line in the SOS?
On Sun, Dec 24, 2017 at 9:55 PM, Sannyasin Brahmanathaswami via
use-livecode wrote:
jacque wrote:
Remote deb
But can you just put the "breakpoint" line in the SOS?
On Sun, Dec 24, 2017 at 9:55 PM, Sannyasin Brahmanathaswami via
use-livecode wrote:
> jacque wrote:
>
> Remote debugging doesn't work with script-only stacks (I had to ask
> here
> on the list myself a while back.) The breakpoint has
jacque wrote:
Remote debugging doesn't work with script-only stacks (I had to ask here
on the list myself a while back.) The breakpoint has to be saved with the
standalone, and script-only stacks don't have properties so breakpoints
can't be saved.
Hmm OK, so that means we have to
what about "breakpoint"?
On Sat, Dec 23, 2017 at 7:34 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 12/23/17 4:43 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
>
>> Does remote debugging (in 9.*) only fire on Android? I added it to my
>> standalone/incl
On 12/23/17 4:43 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
Does remote debugging (in 9.*) only fire on Android? I added it to my
standalone/inclusions set a break point in a script and save the script and
tested with my iPhone as a target… the app ran but did not break the break
I made a few changes to a stack that was some working, and still works on
desktop, but hangs on iOS. I think I even have recipe for the UX/UI
tapping-navigation across handlers/stacks/screens that will cause the app to
crash in iOS.
I used to only dev test SA's on Android because if it worked o
