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
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
until all the keystrokes were
processed).
Bob S
> On Aug 1, 2022, at 12:43 , Paul Dupuis via use-livecode
> wrote:
>
> Now I am very curious about exactly what wait 0 with messages does and also
> about what actions change the defaultStack. Does anyone know of an article
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
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/31/22 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 prevent
mouseUp events in button 2 from being
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 prevent mouseUp events in button 2 from being processed.
I think it must do something, "wait 0" is a
On 7/30/22 19:02, Paul Dupuis via use-livecode wrote:
So Mark,
Your understanding is that 'wait 0' (WITHOUT with messages) would allow
OS events like a screen redraw, USB drive insertion/removal, etc. but
NOT livecode engine events in the queue like mouseDown, mouseUp,
resumeStack, etc
On 7/30/2022 7:49 PM, Mark Wieder via use-livecode wrote:
On 7/30/22 12:53, 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
On 7/30/22 12:53, 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
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 current time (when the statement is
executed
11 matches
Mail list logo
