I figured it out. First, wait for messages is just this side of useless. *ANY* message that comes through will do, not just messages from the open socket command. Secondly, I just set up my own wait loop that exits when the socket is in the openSockets or else times out after 10 seconds. This will work for me.
I went back to the dictionary and read more thoroughly what wait for messages does, and while it is working as advertised, it is fairly worthless in it’s present form unless you find a way to trap for *ALL* messages and only respond to the callback, which is way more involved than it ought to be. Bob S > On Jul 6, 2015, at 13:54 , Mike Bonner <bonnm...@gmail.com> wrote: > > Hmm. YOu might check socketError > _______________________________________________ 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
