Is there some near eqivalent to the field lingo 'the mouseLine' for
text members?
Only yesterday I discovered there's something better. You can say
spriteref.pointToLine(point), as well as char, item, word, and
paragraph. It's awesome.
[To remove yourself from this list, or to change to digest
Is there some near eqivalent to the field lingo 'the mouseLine' for text
members?
roymeo
---
Roy Crisman
Macromedia Director Programmer, Lingo Guru, Multimedia Producer
Greater Rochester Macromedia User Group (GRMMUG.org) Coordinator
277 N. Goodman St.
Rochester, NY 14607-1162
(585)473-34
Irv Kalb wrote:
> 1) Your routine "t" doesn't (and shouldn't need to be) a method of a
> parent script. Instead, it should just be a globally available movie
> level handler.
No real argument, Irv--that's a straightforward way of doing it.
A couple of parameters, though. If it's actually the
If you are using it this way, three things:
1) Your routine "t" doesn't (and shouldn't need to be) a method of a
parent script. Instead, it should just be a globally available movie
level handler.
2) Please don't use member numbers. Yes it's shorter (fewer number
of characters), but as soon
> htmlText = member(3, "websiteBuilder").text & member(2,
> "websiteBuilder").text & member(7, "websiteBuilder").text
>
> I can write htmlText = t(3) & t(2) & t(7)
>
> with the function
>
> on t chunkNumber
> return member(t, "websiteBuilder").text
> end
>
>
> Or is there a smarter way to d
htmlText = usefullyNamedFunction([3,2,7])
on usefullyNamedFunction thisList
tText = ""
repeat with thisNum in thisList
tText = tText & member(thisNum, "cast")
end repeat
return tText
end
roymeo
At 05:13 PM 8/5/2004, you wrote:
> Use meaningful variable and handler names. It's THE first rule of reus
> Use meaningful variable and handler names. It's THE first rule of reusable
programming.
You are right and that is what I normally do. But in this case I need the
name of the handler to be short, because the purpose of the handler is to
get me the content of a text cast member. The whole program
>Its fine so long as you don't need the script reference for anything.
>If it needs to get properties from the behavior/script or needs a
>script reference then you need the "me"
Actually, this is a good way to create pseudo-private functions within
a parent script. If you omit the "me", you can c
Inside a handler (or if you prefer, "method" of a parent script or
behavior script), you need to have the "me" in two circumstances:
1) if you have any other parameters. This is because methods expect
to see the current instance of the object as the first parameter
(this is really what "me" is
Its fine so long as you don't need the script reference for anything. If it
needs to get properties from the behavior/script or needs a script reference
then you need the "me"
-Chuck
--
Chuck Neal
CEO, MediaMacros, Inc.
[EMAIL PROTECTED]
http://www.mediamacros.com
> I tried
>
> on x
> end
>
> and called it with:
>
> x()
>
> And it worked!
>
> However I am sure there must be something wrong with it.
> There must be a reason for the "me" after all.
You need the "me" if you're going to refer to that object or sprite at
all. Mouse events and the like need
Hi everybody,
I have a baxic question about parent scripts.
Until now, a typical handler definition in a parent script of mine looked
like
on mWhatToDo me
...
end
and it was run like that:
me.mWhatToDo()
Now I have a handler that is called very often so that it would be nice, if
the handler
> I've been developing CD-ROMs for a Japanese client for over a
> year now...i use D8.5 and have embedded the appropriate
> japanese fonts that i require...my target is only windows
> systems though..
>
> content is in XML format...i parse that in flash and pass the
> html text to d8.5 which
Hi!
I've been developing CD-ROMs for a Japanese client for over a year now...i
use D8.5 and have embedded the appropriate japanese fonts that i
require...my target is only windows systems though..
content is in XML format...i aprse that in flash and pass the html text to
d8.5 which then renders
14 matches
Mail list logo
