Yup. Launch LC, call up the msg box, enter "Put the time", hit return. Nothing.
I've got the standard plugins along with a couple others, but I've been using those for years and haven't updated them. Someone else on this list reported the same problem with the message box last year, specifically with V 4.5.3. I think this version is not particularly stable (all kinds of on-going problems with the debugger and script editor). I'm planning to upgrade everything to the current versions, but I wanted to get a little further in IOS testing before I commit the $500 for the upgrade. Thanks for your replies. On Tue, Jun 26, 2012 at 4:39 PM, Bob Sneidar <b...@twft.com> wrote: > This happens with no stacks open or in memory and no plugins active? It > sounds like there is something intercepting the enterKey or returnkey > message and not passing it, perhaps in a frontscript. > > Bob > > > On Jun 26, 2012, at 4:11 PM, Howard Bornstein wrote: > > > Unfortunately, it doesn't matter what I put in the message box, since it > > never seems to act on the return key to execute the command. > > > > On Tue, Jun 26, 2012 at 4:00 PM, Bob Sneidar <b...@twft.com> wrote: > > > >> Try typing breakpoint;<your command here> > >> > >> You should be warned however that the message box is a strange beast, > and > >> may not behave as you expect, particularly with regard to execution > >> contexts (if I remember right). > >> > >> Bob > >> > >> > >> On Jun 26, 2012, at 3:48 PM, Howard Bornstein wrote: > >> > >>> Grrr. This bug is back and this time restarting my Mac didn't fix it. > >>> > >>> So I'm trying to trace what happens when I type anything into the > message > >>> box. I've got the script for the message box itself open as well as the > >>> script for the message field. > >>> > >>> I've put breakpoints at the rawkeydown handler as well as on the > >>> ReturnInField handler but I can't seem to make anything trap to the > >>> debugger. > >>> > >>> Shouldn't LC scripts respond like any other scripts when in Script > Debug > >>> Mode? > >>> > >>> I can't imagine what could be causing this problem. Everything else is > >>> working normally, including the message box until yesterday. > >>> > >>> Any ideas would be appreciated. > >>> > >>> -- > >>> Regards, > >>> > >>> Howard Bornstein > >>> ----------------------- > >>> www.designeq.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 > >> > >> > >> _______________________________________________ > >> 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 > >> > > > > > > > > -- > > Regards, > > > > Howard Bornstein > > ----------------------- > > www.designeq.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 > > > _______________________________________________ > 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 > -- Regards, Howard Bornstein ----------------------- www.designeq.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
