Hi Craig, You're right that the button wasn't fully qualified initially, but no error was thrown. That's another problem I've come across in preOpenCard - often errors just don't get thrown. Plus red dot break points don't trigger (although a breakpoint command does).
All in all, preOpenCard is a weird and strange environment. I plan to avoid it wherever possible in the future. In the project with the current issue, preOpenCard consist of a "hide stack" command and I've moved all my processing to openCard with a "show stack" command at the front (thanks to Geoff Canyon for that technique). I hate to have to resort to that type of trickery but I've spent way too much time debugging preOpenCard issues in the past. On Wed, Mar 20, 2013 at 1:33 PM, <dunb...@aol.com> wrote: > As I understand from Peter's original post, he did not send the message to > an explicitly identified button, which I assume would indeed have thrown an > error. Or at least it should have. Pete lcSQL Software <http://www.lcsql.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
