aborting on wait with messages?

In my startup routines (which, admittedly are complex and modify stacks), I have a routine which gets called, puts empty into a pair of global arrays it is about to build or rebuild, and then a "wait 0 with messages" It stops at the wait with "button "src_mcp": execution error at line 1535 (wait:

Re: New Documentation section in Forums/Open Source (was Re: wait with messages)

Great Richard! Best regards, Marc Op 10-mei-2014, om 16:12 heeft Richard Gaskin het volgende geschreven: > As promised, thanks to Heather's work in helping me sort out some PHPBB > permissions issues, we now have a forum for Documentation in the Open Source > section of the forums: >

New Documentation section in Forums/Open Source (was Re: wait with messages)

As promised, thanks to Heather's work in helping me sort out some PHPBB permissions issues, we now have a forum for Documentation in the Open Source section of the forums: One way I see this as becoming a productive working group is for proposals f

Re: wait with messages

Kay, thanks for that post - you raise some important points. Even better, yours is perhaps the first discussion of the User Guide I've seen that describes specific actionable items. The core team at RunRev has been working on a rewrite of the User Guide for a future version, where the scope o

Re: wait with messages

Sorry, I should have mentioned: Bug 11838. On Mon, May 5, 2014 at 12:40 PM, J. Landman Gay wrote: > This is a very good point; you should paste it into a bug report. I've > noticed the same discrepancies in the dictionary and had to think twice > about what some of those entries meant. > > > On

Re: wait with messages

This is a very good point; you should paste it into a bug report. I've noticed the same discrepancies in the dictionary and had to think twice about what some of those entries meant. On 5/4/14, 9:39 PM, Kay C Lan wrote: Maybe it's not an inaccuracy as such, but I think there is a gotcha for Ma

Re: wait with messages

On Fri, May 2, 2014 at 7:32 AM, Richard Gaskin wrote: > > I would imagine that after that much time there would be an error or two > in it, but I haven't come across specific inaccuracies, and I've been > asking for months and haven't been able to find anyone else who can help me > turn up any. >

User Guide (was Re: wait with messages)

Hi, Richard! I am not sure how it might be integrated. Maybe links form the dictionary to sections. Maybe links from example code in the guide to the dictionary. Maybe the ability to open up the section from the editor. Maybe a one-click way to copy example source (or even objects) so it wo

Re: wait with messages

Dar Scott wrote: >> larry wrote: >> >> What really BUGS me about LiveCode is that the documentation ... > > According to the edition information at the front of the document, > this is 3 1/2 years old. > > I intend to include this in my list of books I’m giving to a customer. I would include it.

Re: wait with messages

Gaskin wrote: > larry wrote: > >> What really BUGS me about LiveCode is that the documentation (example, wait >> with messages) is SO sketchy, that you cannot figure out how to use it. > > The docs team at RunRev is working on a rewrite of the User Guide, and part &

Re: wait with messages

larry wrote: What really BUGS me about LiveCode is that the documentation (example, wait with messages) is SO sketchy, that you cannot figure out how to use it. The docs team at RunRev is working on a rewrite of the User Guide, and part of my role as Community Manager is to help provide

Re: wait with messages

well would question if I ever am completely sane. Larry - Original Message - From: "Scott Rossi" To: "How to use LiveCode" Sent: Thursday, May 01, 2014 12:24 PM Subject: Re: wait with messages I feel your pain. We're all in (or have been in) that boat. But I wou

Re: wait with messages

ector Tactile Media, UX Design > On May 1, 2014, at 10:30 AM, wrote: > > What really BUGS me about LiveCode is that the documentation (example, wait > with messages) is SO sketchy, that you cannot figure out how to use it. I'm > constantly wasting my time fighting something t

Re: wait with messages

thanks very much, Dar Larry - Original Message - From: "Dar Scott" To: "How to use LiveCode" Sent: Thursday, May 01, 2014 11:54 AM Subject: Re: wait with messages Larry, I have an old stack called “A Primer on Message Mechanics” that is an exhaustive descr

Re: wait with messages

Larry, I have an old stack called “A Primer on Message Mechanics” that is an exhaustive description of “send” and cousins, should you need to get into this again. (Read “belabored” if you want.) It is here: http://pages.swcp.com/dsc/revstacks.html It does cover ‘wait with messages’ briefly

Re: wait with messages

p also in the script of image "bigPlay" I have on mouseUp (do a bunch of other stuff too) stop playing ac "sound1.wav" stop playing ac "sound2.wav" end mouseUp What really BUGS me about LiveCode is that the documentation (example, wait with messages) is SO ske

Re: wait with messages

Hi Larry: This is probably a situation where wait with messages will not work. If you want to cancel sound 2 independently of sound 1, the second sound needs to have its own play message so it can be canceled separately. This is why I originally suggested the possibility of using a loop script

Re: wait with messages

Larry, Look at ‘send … in 8 seconds’ . Also look at playing messages, and also other things related to send: ‘cancel’ and ‘pendingMessages’. I think we can give a short example, if it will help. Think on what you want the second click to do. Restart the sounds? Be ignored if during sounds?

wait with messages

I have a splash screen and want to play 2 sounds in it, but allow the user to leave as soon as he/she wishes. This was my previous code and it worked fine: play audioclip "Sound1.wav" wait 8 seconds play audioclip "Sound2.wav" looping the problem with the above code is that the "wait" command