I've once had an insider explain to me that the reason is that that type of
function calling is reserved for built in functions, not custom lingo.
Understandable, but an oversight nevertheless...

Which brings me to another idea.

Would someone second my vote for the following concept.

The user would be able to create a castlib of scripts (handlers, functions,
methods, whatever), which would be attached, not to the movie (as an
external CastLib) but to the Application (Director, Projector,
Shockwave(?)). The Castlib could be protected, and the functions within the
castlib would on startup of the Application be "embedded" into Lingo's own
sphere of functions. and could therefore be more readily at hand and
hopefully faster to execute)

This would allow users to make their own "expansions" to the Lingo Function
set.
(Naturally everyone can write their 2000x functions and store them in an
external cast even now, but I'd really love the feel of being able to modify
the platform instead of just the files run with it)

What I'm offering is not in any way revolutionary (except making custom
lingo faster by enabling its integration into the application's core
function set), just a very nifty feature.

For Example I have long since made myself a wide set of geometric
calculation functions Like
somePointValue = MidPointOfRect(Myrect)
or
IntegerValue = distOfPoints(the MouseLoc,
MidPointOfRect(sprite(MySprite).rect))
etc.

IMHO, it would give a new aspect to custom functions...

1 dime (or am I valuing it too high)
Pekka

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Slava Paperno
> Sent: 26. heinakuuta 2001 21:53
> To: [EMAIL PROTECTED]
> Subject: Re: <lingo-l> Type 2 Crash. a cautionary tale
>
>
> I haven't done the tracing that you have, but I think my Type 2
> crashes of
> D8 on Mac OS 9.04 started when I started using the same type of calls...
> Does this Cautionary Tale apply to D8.5?
>
> Slava
>
> At 12:43 PM 7/26/2001 -0400, you wrote:
>
> >Two days ago I started getting catastrophic crashes on my Mac that made
> >Director simply vanish from my screen with a Type 2 error*...
> >The line was something very like:
> >  sprite(29 + x).setprops(foo, bar, rabnicky)
> >
> >It was suggested that calling a handler that way, while it works most of
> >the time, is not actually supported and that 'call' or 'sendsprite' are
> >the ways to go. (thanks Dan S.)
> >
> >now I use:
> >sendsprite(29 + x,#setprops,foo, bar, rabnicky)
>
>
> [To remove yourself from this list, or to change to digest mode, go to
> http://www.penworks.com/LUJ/lingo-l.cgi  To post messages to the list,
> email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED])
> Lingo-L is for learning and helping with programming Lingo.  Thanks!]
>


[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi  To post messages to the list,
email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo.  Thanks!]

Reply via email to