This is correct.
Bob S
> On Jul 31, 2022, at 12:14 , J. Landman Gay via use-livecode
> wrote:
>
> On 7/31/22 12:04 AM, Mark Wieder via use-livecode wrote:
>> I don't think "wait 0" by itself does anything useful. Make a stack with two
>> buttons. Running the script in the first button will
On 7/30/2022 3:53 PM, Paul Dupuis via use-livecode wrote:
My understanding of 'wait 0 with messages' is that it will cause any
pending messages, that are not scheduled for a time later than the
current time, in the pendingMessages queue to be processed before
continuing. Messages later than the
It's my understanding that wait allows idle messages from the engine to be
sent. When that happens, any send in time messages are processed. Wait with
messages allows any other messages including engine messages to be processed.
For instance, I have a FindBar object that uses wait 1 second with
As my application(s) became more complex, I also ran into topstack and
curentcard issues. As a result, I am in the habit now of either using "of me"
appended to every command of in a card or stack script, or else sending the
long id of an object to a command or function that is not in the messag
Yea, a number of years ago, I went to always fully qualifying object
references through all the techniques you mentioned, but we've just not
had a chance to scrub the entire code base (100,000 lines+) and so this
one got missed until now.
We're now going through the entire code base to catch a
