> I wonder, what is undocumented Lingo?
Largely, it's stuff the programmers put in, but there wasn't sufficient time &
personnel to test/fix it well enough to make it public. Often these features,
like rateshift, are documented in subsequent releases.
Then there are then [way too many] document
On Monday, Sep 15, 2003, at 10:27 America/Chicago, Thomas Higgins wrote:
It's not that Macromedia as a company doesn't want you to know about
these
items
[...]
We're not trying to be sneaky here. :)
Riiight. We all know Macromedia is engaged in a massive
disinformation conspiracy. Obvio
t: Re: undocumented Lingo
On Monday, September 15, 2003, at 09:39 AM, [EMAIL PROTECTED] wrote:
> I haven't tried floodfill().. but it may be useful on a project I am
> starting. What are the parameters(arguments) that it requires??
According to James Newton's book -
imageObject.flo
All,
A quick bit from my end on where undocumented features come from:
1. Something that was implemented but couldn't get to a stable
enough state (due to bugs) prior to shipping in order to get
"official feature" status.
2. Features that crept in late in the game and didn't recieve
enou
On Monday, September 15, 2003, at 09:39 AM, [EMAIL PROTECTED] wrote:
I haven't tried floodfill().. but it may be useful on a project I am
starting. What are the parameters(arguments) that it requires??
According to James Newton's book -
imageObject.floodfill(, )
--
Troy
RPSystems, Ltd.
http:/
I haven't tried floodfill().. but it may be useful on a project I am starting. What
are the parameters(arguments) that it requires??
Thanks,
-Boyd
[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 [EMA
That happens too... no one wants to "officially" release it yet because it
was either tossed in at the last minute, or they didn't get it working
until the last minute, and it never really got tested and vetted.
And, occasionally, from other places I've been, I know developers have
their own pe
> There's a more optimistic variation of this, and that is that the
> feature was ready for use, but was added too close to the ship date
> to get a full testing, and so couldn't be mentioned in case there
> turned out to be a problem. There have been many examples of such
> features, that all
More often, particularly in Lingo, they're just not ready for prime
time. In your example, a call fails under certain conditions.
Chances are that someone started to implement it, ran out of time,
or ran into insurmountable bugs, and the product (Director) was
released making no mention of the
Macromedia wants people to know about all great features - no point having
a great feature if no one knows about them.
Occasionally an undocumented feature is one that is powerful but not safe
in the hands of people who don't know what to do with it. Nothing in Lingo
comes to mind that qualifi
10 matches
Mail list logo
