The app didn’t actually crash with a crash report. It just gave me the bug report email, so it’s probably not reportable and I shouldn’t have called it a crash. This bug teaches me to ALWAYS check if a file exists before trying to link to it. It was part of the code when I was learning LiveCode, but that’s no excuse.
BTW, I noticed that for a number of lines, I had a curly bracket rather than a square one. e.g put myNumber into myList[xyz”} Shouldn’t the IDE toss an error alert? Seemed to work anyway. I fixed it anyway. Best, Bill William A. Prothero http://es.earthednet.org/ > On Jan 13, 2015, at 4:47 PM, Dr. Hawkins <[email protected]> wrote: > > On Tue, Jan 13, 2015 at 4:17 PM, William Prothero <[email protected]> > wrote: > >> Never mind!! Looks like a found the problem. It was me. I found it when I >> was entering a bug report and typed “it’s as if the image is not being >> loaded.” Bingo!! The paths are slightly different on Mac and PC >> standAlones. >> > > I've filed at least one that seems to cause a crash on Mac IDE and > standalone when referencing a nonexistent property. One went to "waiting > build" this morning. Hurrah! > > And I saw another variant when a stack got renamed; referencing its > properties (once the named stack no longer existed) caused the crash. > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
