Thank you, Thomas. That kind of acknowledgement is greatly appreciated.
- Michael M.
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL
PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L
> If MACR is listening, that would be a nice bug fix for Director MX 2016.
We've been trying to get Macromedia to standardize dot-syntax usage for at
least three versions. Buzz and I even went to the effort of preparing a list
of missing/inconsistent dot syntax for them. I feel like I was saying
While I'm doing my to actually respond to every bug submitted via
the form I can't guarantee a reply
I'm hoping it was the word 'best' that you missed out.
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, ema
All,
> > You still have to use "old" lingo for #field member chunk operations.
> > Try this: put the foreColor of line 1 of member("theContent")
> >
> > Why?
> > Good question...
>
> Aah. Thank you, Bertil.
>
> If MACR is listening, that would be a nice bug fix for
> Director M
Aah. Thank you, Bertil.
If MACR is listening, that would be a nice bug fix for Director MX 2016.
You still have to use "old" lingo for #field member chunk operations.
Try this: put the foreColor of line 1 of member("theContent")
Why?
Good question...
[To remove yourself fro
You still have to use "old" lingo for #field member chunk operations.
Try this:
put the foreColor of line 1 of member("theContent")
Why?
Good question...
Bertil Flink
Creative Media
--
Packing all the ideas and their finest
nuances into two lines is damn diffic
Hi all...
Is it possible to format individual lines of text in a field via lingo?
Right now, these are my results:
put member("theContent").forecolor
-- 255
put member("theContent").line[4].forecolor
-- alerts script error: property not found.
It seems to me that if you can change the color of
