Re: "send" vs "dispatch"

2018-10-09 Thread Mark Wieder via use-livecode
On 10/09/2018 07:33 AM, Bob Sneidar via use-livecode wrote: Yup. I groked that. So I always return empty for success and false if not. Nice. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please

Re: "send" vs "dispatch"

2018-10-09 Thread Bob Sneidar via use-livecode
Yup. I groked that. So I always return empty for success and false if not. > On Oct 8, 2018, at 17:53 , Mark Wieder via use-livecode > wrote: > > Another nice feature of dispatch is that if the handler does not exist in the > target, it will silently and gracefully fail, continuing to

Re: "send" vs "dispatch"

2018-10-08 Thread Monte Goulding via use-livecode
One of the main reasons I implemented send and call with params in the PR that has been mentioned is because it allows for referenced parameters. The following is an error: on mouseUp local tBar send “foo tBar” to me answer tBar end mouseUp on foo @rBar put “Howdy" into rBar end

Re: "send" vs "dispatch"

2018-10-08 Thread Tom Glod via use-livecode
ever since I learned that you can pass a whole array using the send command the dispatch doesn't seem that much more convenient at all..i do alot of in time commands so this is very convenient to my needs / style send "mymessage myarray" to this stack for years I thought using this form

Re: "send" vs "dispatch"

2018-10-08 Thread Mark Wieder via use-livecode
On 10/08/2018 04:41 PM, Bob Sneidar via use-livecode wrote: Another nice feature of dispatch is that if the handler does not exist in the target, it will silently and gracefully fail, continuing to execute code after the call. Yeah, that's a double-edged doohickey, though. I *do* use it that

Re: "send" vs "dispatch"

2018-10-08 Thread Bob Sneidar via use-livecode
I like the dispatch form, separating parameters out from the command. The reason is given stepping into this code, send "test ha" to button 1 I cannot point to the variable "ha" and see the value it contains. But if, dispatch "test" to button 1 with ha I can. I only use send anymore when I

Re: "send" vs "dispatch"

2018-10-05 Thread 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 >

Re: "send" vs "dispatch"

2018-10-05 Thread 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 >

Re: "send" vs "dispatch"

2018-10-05 Thread 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 <

Re: "send" vs "dispatch"

2018-10-05 Thread 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

Re: "send" vs "dispatch"

2018-10-05 Thread 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

Re: "send" vs "dispatch"

2018-10-05 Thread 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

Re: "send" vs "dispatch"

2018-10-05 Thread 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,

Re: "send" vs "dispatch"

2018-10-05 Thread 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: > >

Re: "send" vs "dispatch"

2018-10-05 Thread 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

Re: "send" vs "dispatch"

2018-10-05 Thread 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