Monte Goulding writes:
>
> Well the Cosmic Turtle won't be all that happy to hear that...
I've heard some nicknames for Kevin Miller before,
but that's a new one on me.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode mailing list
use-li
Well the Cosmic Turtle won't be all that happy to hear that...
Sent from my iPhone
> On 20 Jul 2016, at 5:21 AM, Jim Lambert wrote:
>
> ‘Global Handler’ is reserved for Atlas. ;)
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please vis
> I?m not sure why the term global handler was used
‘Global Handler’ is reserved for Atlas. ;)
Jim Lambert
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
prefere
> On 19 Jul 2016, at 1:49 AM, Richard Gaskin wrote:
>
> ...where Monte has this note:
>
> Previously global handlers took priority
> over handlers scripted in LCS. This patch
> enables a LCS handler the handle the global
> handler instead. This is necessary for
> for overriding the li
Richard Gaskin writes:
> Can you or Monte elaborate on that? Is a "global handler" and engine
> handler? Does this mean we can now override engine-defined functions?
>
Heh. I asked Monte the same question last week.
No, it's very specific to the new libURL handlers.
--
Mark Wieder
ahsoft
Thanks for the update, Peter.
One of the items in this week's newsletter was particularly intriguing:
Allow global handlers to be overridden by scripted handlers
https://github.com/livecode/livecode/pull/4265
...where Monte has this note:
Previously global handlers took priority
over han
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #42 here: https://goo.gl/bfNksI
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and
