Re: "send" vs "dispatch"

[Brian Milby via use-livecode]

Probably the “in time” variant along with parity.

The PR also opens up sending to widget handlers which is what I’m waiting for.

Thanks,
Brian
On Oct 5, 2018, 9:36 PM -0400, Geoff Canyon via use-livecode 
, wrote:
> Is there a benefit to adding parameters to send? Or does this just bring it
> into parity/redundancy with dispatch?
>
> On Fri, Oct 5, 2018 at 3:16 PM Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > There is a PR to change this:
> > https://github.com/livecode/livecode/pull/6479
> >
> > Will add args to send and call.
> >
> > Thanks,
> > Brian
> > On Oct 5, 2018, 6:09 PM -0400, Geoff Canyon via use-livecode <
> > use-livecode@lists.runrev.com>, wrote:
> > > A word to the wise (mostly for IDE and extension developers): this will
> > > successfully compile:
> > >
> > > send "test" to button 1 with "ha"
> > >
> > > And then if the IDE is swallowing up your error messages (as it does for
> > > extensions like Navigator) it will even deliver the message "test" to
> > > button 1, just without any arguments, and then die silently.
> > >
> > > Outside of "rev" stacks, it will deliver the message without arguments
> > and
> > > then throw an error saying there is no handler "with". I just checked,
> > and
> > > amazingly this will work:
> > >
> > > on mouseUp
> > > send "test" to button 1 with "ha"
> > > end mouseUp
> > >
> > > on with
> > > answer "WTH?"
> > > end with
> > >
> > > But that's obviously unlikely. Far more likely if you're dealing with
> > > code you wrote before you became aware of "dispatch" (or maybe before
> > > "dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
> > > decide to add an argument to a remote call and don't notice that it's a
> > > "send" rather than a "dispatch", and then spend half an hour trying to
> > > figure out why your arguments aren't passing through .
> > > ___
> > > 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
> >
> ___
> 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

Re: "send" vs "dispatch"

[Geoff Canyon via use-livecode]

Is there a benefit to adding parameters to send? Or does this just bring it
into parity/redundancy with dispatch?

On Fri, Oct 5, 2018 at 3:16 PM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> There is a PR to change this:
> https://github.com/livecode/livecode/pull/6479
>
> Will add args to send and call.
>
> Thanks,
> Brian
> On Oct 5, 2018, 6:09 PM -0400, Geoff Canyon via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
> > A word to the wise (mostly for IDE and extension developers): this will
> > successfully compile:
> >
> > send "test" to button 1 with "ha"
> >
> > And then if the IDE is swallowing up your error messages (as it does for
> > extensions like Navigator) it will even deliver the message "test" to
> > button 1, just without any arguments, and then die silently.
> >
> > Outside of "rev" stacks, it will deliver the message without arguments
> and
> > then throw an error saying there is no handler "with". I just checked,
> and
> > amazingly this will work:
> >
> > on mouseUp
> > send "test" to button 1 with "ha"
> > end mouseUp
> >
> > on with
> > answer "WTH?"
> > end with
> >
> > But that's obviously unlikely. Far more likely if you're dealing with
> > code you wrote before you became aware of "dispatch" (or maybe before
> > "dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
> > decide to add an argument to a remote call and don't notice that it's a
> > "send" rather than a "dispatch", and then spend half an hour trying to
> > figure out why your arguments aren't passing through .
> > ___
> > 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
>
___
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

Re: "send" vs "dispatch"

[Geoff Canyon via use-livecode]

If you have multiple parameters, dispatch is easier, cleaner, and safer. So
even if I don't have parameters, unless I need a time delay I use dispatch.
Also, you can use dispatch function to call functions.

gc

On Fri, Oct 5, 2018 at 3:16 PM Peter Bogdanoff via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I’m finding it’s best to do this when you “send” and have a parameter:
>
> send “test ha” to button 1
>
>
> Peter Bogdanoff
> ArtsInteractive
>
___
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

Re: "send" vs "dispatch"

[Geoff Canyon via use-livecode]

Ha -- there are about 7,000 lines of code in Navigator -- I think that
means I've written about...70,000 lines of code? :-)

But in any case, there are 80 instances of Dispatch and 63 instances of
Send in Navigator.

My next step I think is to learn more about how Sublime Text handles find
and replace across multiple files, because every instance of Send that
doesn't involve a time delay is going to become a dispatch.

On Fri, Oct 5, 2018 at 3:15 PM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I've written over 30 000 lines of code in livecode.
>
> used dispatch  once. :)
>
___
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

Re: "send" vs "dispatch"

[Mark Wieder via use-livecode]

On 10/05/2018 03:08 PM, Geoff Canyon via use-livecode wrote:


on with
answer "WTH?"
end with


I find that quite disturbing.
But I quite agree with the answer 

--
 Mark Wieder
 ahsoftw...@gmail.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

Re: "send" vs "dispatch"

[Mark Wieder via use-livecode]

On 10/05/2018 03:15 PM, Tom Glod via use-livecode wrote:

I've written over 30 000 lines of code in livecode.

used dispatch  once. :)


Dispatch is awesome. The only time I use 'send' any more is when I need 
the 'in time' form.


--
 Mark Wieder
 ahsoftw...@gmail.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

Re: "send" vs "dispatch"

[Tom Glod via use-livecode]

cool That is very useful indeed.

On Fri, Oct 5, 2018 at 6:16 PM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> There is a PR to change this:
> https://github.com/livecode/livecode/pull/6479
>
> Will add args to send and call.
>
> Thanks,
> Brian
> On Oct 5, 2018, 6:09 PM -0400, Geoff Canyon via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
> > A word to the wise (mostly for IDE and extension developers): this will
> > successfully compile:
> >
> > send "test" to button 1 with "ha"
> >
> > And then if the IDE is swallowing up your error messages (as it does for
> > extensions like Navigator) it will even deliver the message "test" to
> > button 1, just without any arguments, and then die silently.
> >
> > Outside of "rev" stacks, it will deliver the message without arguments
> and
> > then throw an error saying there is no handler "with". I just checked,
> and
> > amazingly this will work:
> >
> > on mouseUp
> > send "test" to button 1 with "ha"
> > end mouseUp
> >
> > on with
> > answer "WTH?"
> > end with
> >
> > But that's obviously unlikely. Far more likely if you're dealing with
> > code you wrote before you became aware of "dispatch" (or maybe before
> > "dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
> > decide to add an argument to a remote call and don't notice that it's a
> > "send" rather than a "dispatch", and then spend half an hour trying to
> > figure out why your arguments aren't passing through .
> > ___
> > 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
>
___
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

Re: "send" vs "dispatch"

[Brian Milby via use-livecode]

There is a PR to change this:
https://github.com/livecode/livecode/pull/6479

Will add args to send and call.

Thanks,
Brian
On Oct 5, 2018, 6:09 PM -0400, Geoff Canyon via use-livecode 
, wrote:
> A word to the wise (mostly for IDE and extension developers): this will
> successfully compile:
>
> send "test" to button 1 with "ha"
>
> And then if the IDE is swallowing up your error messages (as it does for
> extensions like Navigator) it will even deliver the message "test" to
> button 1, just without any arguments, and then die silently.
>
> Outside of "rev" stacks, it will deliver the message without arguments and
> then throw an error saying there is no handler "with". I just checked, and
> amazingly this will work:
>
> on mouseUp
> send "test" to button 1 with "ha"
> end mouseUp
>
> on with
> answer "WTH?"
> end with
>
> But that's obviously unlikely. Far more likely if you're dealing with
> code you wrote before you became aware of "dispatch" (or maybe before
> "dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
> decide to add an argument to a remote call and don't notice that it's a
> "send" rather than a "dispatch", and then spend half an hour trying to
> figure out why your arguments aren't passing through .
> ___
> 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

Re: "send" vs "dispatch"

[Peter Bogdanoff via use-livecode]

I’m finding it’s best to do this when you “send” and have a parameter:

send “test ha” to button 1


Peter Bogdanoff
ArtsInteractive

> On Oct 5, 2018, at 3:08 PM, Geoff Canyon via use-livecode 
>  wrote:
> 
> A word to the wise (mostly for IDE and extension developers): this will
> successfully compile:
> 
>   send "test" to button 1 with "ha"
> 
> And then if the IDE is swallowing up your error messages (as it does for
> extensions like Navigator) it will even deliver the message "test" to
> button 1, just without any arguments, and then die silently.
> 
> Outside of "rev" stacks, it will deliver the message without arguments and
> then throw an error saying there is no handler "with". I just checked, and
> amazingly this will work:
> 
> on mouseUp
>   send "test" to button 1 with "ha"
> end mouseUp
> 
> on with
>   answer "WTH?"
> end with
> 
> But that's obviously unlikely. Far more likely if you're dealing with
> code you wrote before you became aware of "dispatch" (or maybe before
> "dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
> decide to add an argument to a remote call and don't notice that it's a
> "send" rather than a "dispatch", and then spend half an hour trying to
> figure out why your arguments aren't passing through .
> ___
> 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

Re: "send" vs "dispatch"

[Tom Glod via use-livecode]

I've written over 30 000 lines of code in livecode.

used dispatch  once. :)





On Fri, Oct 5, 2018 at 6:09 PM Geoff Canyon via use-livecode <
use-livecode@lists.runrev.com> wrote:

> A word to the wise (mostly for IDE and extension developers): this will
> successfully compile:
>
>send "test" to button 1 with "ha"
>
> And then if the IDE is swallowing up your error messages (as it does for
> extensions like Navigator) it will even deliver the message "test" to
> button 1, just without any arguments, and then die silently.
>
> Outside of "rev" stacks, it will deliver the message without arguments and
> then throw an error saying there is no handler "with". I just checked, and
> amazingly this will work:
>
> on mouseUp
>send "test" to button 1 with "ha"
> end mouseUp
>
> on with
>answer "WTH?"
> end with
>
> But that's obviously unlikely. Far more likely if you're dealing with
> code you wrote before you became aware of "dispatch" (or maybe before
> "dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
> decide to add an argument to a remote call and don't notice that it's a
> "send" rather than a "dispatch", and then spend half an hour trying to
> figure out why your arguments aren't passing through .
> ___
> 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

"send" vs "dispatch"

[Geoff Canyon via use-livecode]

A word to the wise (mostly for IDE and extension developers): this will
successfully compile:

   send "test" to button 1 with "ha"

And then if the IDE is swallowing up your error messages (as it does for
extensions like Navigator) it will even deliver the message "test" to
button 1, just without any arguments, and then die silently.

Outside of "rev" stacks, it will deliver the message without arguments and
then throw an error saying there is no handler "with". I just checked, and
amazingly this will work:

on mouseUp
   send "test" to button 1 with "ha"
end mouseUp

on with
   answer "WTH?"
end with

But that's obviously unlikely. Far more likely if you're dealing with
code you wrote before you became aware of "dispatch" (or maybe before
"dispatch" was a thing -- I think Navigator predates LC 3.5) is that you
decide to add an argument to a remote call and don't notice that it's a
"send" rather than a "dispatch", and then spend half an hour trying to
figure out why your arguments aren't passing through .
___
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

Re: Will it ever be possible place controls over browser widget?

[Tom Glod via use-livecode]

Hi JIm, your suggestion could work but the floating window is quicker and
does the job, thanks for giving it a whirl around.

On Fri, Oct 5, 2018 at 5:32 PM Jim Lambert via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> > Herman wrote:
> >
> > See my demo here:
> >
> > http://forums.livecode.com/viewtopic.php?p=152773#p152773 <
> http://forums.livecode.com/viewtopic.php?p=152773#p152773>
> >
> > Overlays the widget while this plays a video.
>
> So floating a second stack over the browser as I suggested does work and
> is beautifully demonstrated in Herman’s DemoVideoBack.livecode.zip.
>
> Jim Lambert
>
> ___
> 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

Re: Will it ever be possible place controls over browser widget?

[Jim Lambert via use-livecode]

> Herman wrote:
> 
> See my demo here:
> 
> http://forums.livecode.com/viewtopic.php?p=152773#p152773 
> 
> 
> Overlays the widget while this plays a video.

So floating a second stack over the browser as I suggested does work and is 
beautifully demonstrated in Herman’s DemoVideoBack.livecode.zip.

Jim Lambert

___
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

Re: Will it ever be possible place controls over browser widget?

[Jim Lambert via use-livecode]

> Herman wrote:
> 
> See my demo here:
> 
> http://forums.livecode.com/viewtopic.php?p=152773#p152773 
> 
> 
> Overlays the widget while this plays a video.

So floating a second stack over the browser as I suggested does work and is 
beautifully demonstrated in Herman’s DemoVideoBack.livecode.zip.

Jim Lambert
___
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

[OT] My Kickstarter is live

[Malte Pfaff-Brill via use-livecode]

Hi list!

As some of you have asked, here is the link to my Kickstarter campaign.

https://www.kickstarter.com/projects/1283741654/puppet-prototyper 


If you go looking, you can see the fat man making a fool out of himself in the 
video as an instant gratification. :-)

Cheers!

Malte

___
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

Re: Breakpoints Failing / Crashes

[dunbarxx via use-livecode]

Except that the "Red dot" breakpoints cannot be trusted at all, the
"breakpoint" command has never failed in v8. or earlier.  Must be a v9
issue, but I am surprised nobody has mentioned it till now.

Craig Newman



--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
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

Breakpoints Failing / Crashes

[Sannyasin Brahmanathaswami via use-livecode]

breakpoint  -- either entered by "red dot" or explicitly placed
"breakpoint" in the code  and frequently "non-observed" and just now had
a crash are click the breakpoint dot (which was not working) and
attempting to insert "breakpoint"

anyone else having to trouble,

Mac OS X , LC 9.0.1 stable (not really stable at all!)

___
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

Re: Will it ever be possible place controls over browser widget?

[Rick Harrison via use-livecode]

Hi Tom,

How about dragging the widget off of the visible screen?
You could create your own interface look for it, or for 
whatever you are trying to do, and have that send 
messages to the offscreen widget to process. Then 
send the results of the widget back to your graphic 
interface?

It might be a good work around for you although it
could be more work.

Just my 2 cent ideas here.

Rick

> On Oct 4, 2018, at 2:04 PM, Tom Glod via use-livecode 
>  wrote:
> 
> Hi,
> 
> Ehh.Does anyone know if it will ever be possible to place controls on
> layers above a browser widget?
> 
> Thanks,
> 
> Tom
> ___
> 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