LiveCode Forums

Gilar- haven't forgotten about you here. I downloaded Resolume Avenue over the weekend :shock: and have been having too much fun playing with it. :wink: ...and in looking things over, I realize that the OSC library I wrote was very much oriented towards the board I was working with, and could easily...

This is the result CODE: SELECT ALL ,i/track3/connect is this ok? No, it should be /track3/connect,i And then the value you're sending (in this case a 1) will be binary-encoded, so you won't see the actual value in your field without decoding it back again. But since you're seeing the other values ...

Richard- A little experimenting here deepens the mystery: In a standalone the ask and answer dialogs are still launched as separate stacks, so no... the underlying stack is not part of the message path. This is what I expected, so no surprise there. But... the mouseDown message is *not* passed on th...

Richard- even in a standalone the ask and answer dialogs are separate stacks. They're launched as modal stacks no matter what environment.

stam- the ask and answer dialog stacks are launched as separate stacks. The mouseDown etc messages don't get passed to the (visually) underlying stack because it's a separate stack, so no longer in the message path of the dialogs.

Craig- yes, that's the whole point of this topic.

Craig- mouseLeave is necessary for the functioning of the ecosystem. You may find the cursor changes when over a stack etc. And if you trap the mouseMove message in a library stack you'll see it's in use within a modal dialog as well. Again, it's necessary for the functioning of the system as a whol...

Well, it's been a dozen years now since I wrote this library and a good five years since I've looked at the code, I'll see what I can do... first of all, it's not necessary (and maybe a bad idea) to copy the OSC library into the main stack script. You've already got it in a substack and you're putti...

Er...they're not "suspended", they're just contained within the modal dialog. So you can press keys in an Ask dialog and they're handled, but pressing keys in any other stack or control has no effect. Modal dialogs force the user to interact with them before they can do anything else. I even have a ...

Richard- was that last question aimed at me? From the dictionary: The modal command pauses the running handler until the modal dialog box is dismissed (usually by clicking a button in the modal dialog box). and While a modal dialog box is open, other windows cannot be edited or brought to the front....

Got it. There's now an updated test stack there that will avoid debugger issues and just place some text in the message box.

I've got a sample stack in the bug report linked to earlier.

Because modal stacks are supposed to block any other messages until you dismiss them, either by selecting one of the options or by canceling them. And they do, except as discovered, for mouseDown messages.

There are two things at play, related by the edge case uncovered here. First, modal dialogs should not leak messages as side effects. If you bring up a modal dialog and try to click on some other stack to initiate a mouseDown message, nothing happens. And this is true whether or not there are librar...

Doh! Of course - that makes sense.
OK - that's my stupid post for the day. Now I can take the rest of the day off.