Here's another data point for this oddity. Once the IDE starts tripping out from breakpoints and I restart Livecode to fix the problem, the behavior in which the breakpoints stop working has "detached" from the object pointing to it. I say "detached", as the object still shows in the Inspector that it is pointing to the behavior-containing control and choosing to edit the behavior script from the object's Inspector opens up the relevant behavior in the Script Editor. Breakpoints work once again when I once more point the object's Inspector at the object it knows contains the behavior script
Somewhere inside LC this connection is being lost. At the moment the only variable I've been able to isolate as a cause is: how many hours I've had LC open working on this project. On Fri, Jul 17, 2020 at 7:35 PM Bernard Devlin <bdrun...@gmail.com> wrote: > I found later that the same thing was happening away from this code block, > and with just a red breakpoint. > > As I don't restart my PC for weeks on end, I quit LC and restarted. Both > of these strange error situations disappeared. Which suggests that it is > some complex condition (either within my app or within the IDE) that leads > to this situation. > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
