hey kerry-
i've been using LDM's a lot lately. mostly in shockwave.
The first thing i'd say is the usual distinction: filmloops are better
for little to no interactivity, LDM's are better for robust interactivity.
you pay a bit a a price by using LDM's- they can be hard to debug when
they're linked, you have to be quite organized in an OOP way because
globals and movie scripts can get confused about which one to run. also
there can be some screen redraw issues, though that may be only in
shockwave. there can be weird effects with primary events on sprites:
sometimes those events are reported for the sprites within the movie,
sometimes for the linked movie itself. but there are workarounds for all
those issues.
for your purposes, filmloops might be better. there are limitations to
the lingo you can use in them, but you should be able to do some of the
basic things you've described, or at least move the management of that
functionality to the movie itself, and not the filmlooop (if that
doesn't upset the oops structure too much).
but for more complex embedded objects LDM's can be great. especially in
a case where you need multiple interactive sprites in a group, but you
want to be able to treat them as one screen object. but as i said, there
is some overhead involved, so in general i'd say
if you can do it with a filmloop, go that way,
if it requires more programming than a filmloop can handle, use a LDM.
and feel free to ask specific LDM questions. I'd like to use this
knowledge for good, not evil.
--bhakti
p.s. hey what a small lingo world it is, i used to work with bill garr
too. he's a fantabulous programmer and a swell guy to boot.
Kerry Thompson wrote:
>
> Here's another possible cause for stuttering audio: too many Flash sprites.
>
> I've taken over a project that has been plagued by stuttering audio,
> especially on low-end machines. The original authors, two very, very good
> programmers, had tried everything the Lists suggested, but it persisted.
>
> I basically made a lucky guess, replaced some Flash sprites with bitmaps,
> and the audio problems went away.
>
> Now we have a decision to make. We'd like to replace the Flash animations
> with either LDM's or film loops. I'm looking for some input on the best
> approach, because I haven't used LDM's much.
>
> Most of the Flash animations we're replacing are clickable sprites--nav
> buttons, tiles in a concentration-like game, etc. They tend to be very
> simple--they do a little animation, play a sound, and notify the calling
> object via callback when they're done. The code is very nicely structured
> OOP (shameless plug--Bill Garr, the original author, is moving to the east
> coast and might be looking for some contract work).
>
> So, what do you recommend? LDM's or film loops? And, of course, why would
> you recommend one over the other?
>
> Cordially,
>
> Kerry Thompson
>
> [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!]
--
R. Bhakti Klein
Educational Software R & D
http://www.DLWorkshop.net
��
Baritone, unaffiliated but open to suggestions...
���
"On Earth, you can only do little things;
but you can do them with a lot of Love."
-- Mother Theresa
[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!]
