Chiming in again since it dovetails with today's work:
Crashing bugs (and others) sometimes require a missing
factor/context/detail in the original real-world project that is tricky
to reproduce in independent test stacks. You have to compensate for that.
I filed this crasher today, but had to use a slightly more "extreme"
example compared to the original real-project-crasher to get 100%
reliable open-click-crash independent test stack:
(Save work before running)
https://quality.livecode.com/show_bug.cgi?id=22586
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/
_______________________________________________
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
