Grrr, new timeout syntax

I wouldn't care if someone would just update the docs to
reflect new 
syntax rules - Come on!

Ok, so does anyone know the new syntax for using a timeout
object in 
MX04?

It was

timeout("name").new(intInterval, symHandler
{,optObjRef})

now it is...?

--al
_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

variableName = new timeOut(timeOutObjName, intMilliseconds, 
#handlerName 	{, targetObject})


-- nevermind - it's right in timeout but wrong in new - but
why 
doesn't it work in dot syntax now?

sheesh,

--al

On Tue, 21 Nov 2006 10:59:58 -0500
  "Allen R Partridge" <allen.partridgeiup.edu> wrote:
> I wouldn't care if someone would just update the docs
to reflect new 
>syntax rules - Come on!
> 
> Ok, so does anyone know the new syntax for using a
timeout object in 
>MX04?
> 
> It was
> 
> timeout("name").new(intInterval, symHandler
{,optObjRef})
> 
> now it is...?
> 
> --al
> _______________________________________________
> dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

> Ok, so does anyone know the new syntax for using a
timeout object in
> MX04?
> It was
> timeout("name").new(intInterval, symHandler
{,optObjRef})
> now it is...?
Still the same, if you do
the scriptexecutionstyle=9

I would also like to point out that this "feature"
was implemented by
the product manager who has quit Adobe...


Greets,
Christophe Leske

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

> now it is...?
I think the correct new syntax is _movie.new(timeout()))

Just for the records:
old (read "pre Director MX 2004" movies) have that
flag set
automatically, so if you convert an old movie in Director MX
2004, you
are safe. The new syntax only applies to newly created
movies.

Say hello to confusion. Best trick is to use "the
scriptexecutionstyle=9" at the very beginning, and
everything is back
dandy to old skool lingo style.

C

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Well, I think I posted this once to some other list, but the
folks here
may be interested as well.  Small steps forward on my DF3DI
project,
which is a way to author shockwave3D from Actionscript. 
Demo moving
coming next month (I hope), we're getting there, albeit a
bit slowly.

Lots of core idiocy to deal with under the hood, asset
loaders, config
file,
Etc.

But some screens up now, and some small details.  Below is
the XML that
sets up the demo scene in the screenshot at the bottom of
the page.

If this is of interest to you going forward, please let me
know, I'm
going to try and set up a mail list soon so I can start
asking people in
the dev community questions on their preferences with regard
to certain
aspects.  I'll announce that here also when it gets going.

The page: http://andy
sgi.rit.edu/andyworld10/df3di/
The XML (is below)

This is very much pre-alpha, but we're excited   Have a
happy
Thanksgiving if you celebrate such.

-Andy

<?xml version="1.0"
encoding="UTF-8"?>
<df3diproject xmlnssi=&q
uot;http:
//www.w3.org/2001/XMLSchema-instance"
    
xsi:noNamespaceSchemaLocation="DF3DI_schema.xsd"&g
t;
	<name>test</name>
      <stage>
            <rect x1="100" y1="100"
x2="900" y2="700" />
            <windowstyle menu="1"
center="0" topleft="1" />
      </stage>
      <log>
           <rect x1="400" y1="330"
x2="800" y2="400" />
           <queue qlength="16"
fontSize="10" lineHeight="10" />
           <!-- available debugTypes are
"luminicBox", "streamer",
"immediate", "perframe", and
"none" -->
           <!-- available debugLevels are
"all", "log", "debug",
"info",
"warn", "error", "fatal", and
"none" -->
           <!-- NOTE: debugLevel only affects output in
luminicBox - the
exception being that "none" will
                      block all output regardless of
debugType -->
           <mode debugType="luminicBox"
debugLevel="all" />
      </log>
	<flash_controller>
		<path>flatest4.swf</path>
		<rect x1="0" y1="0"
x2="20" y2="18" /> 
      </flash_controller>
	<threedworld>
            <!-- NOTE: Results are undefinied if these
overlap... -->
		<viewport x1="0" y1="140"
x2="400" y2="430" uid="666"
/>
            <viewport x1="400"
y1="40" x2="800" y2="330"
uid="777" />

            <texture path="happy.jpg"
                     uid="1" 
                     quality="medium"
                     nearFiltering="true"
                     compressed="true"
                     renderFormat="rgba8888" />
 
            <texture path="happy2.jpg"
                     uid="2"  
                     quality="medium"
                     nearFiltering="true"
                     compressed="true"
                     renderFormat="rgba8888" />


            <texture path="happy3.jpg"
                     uid="3"
                     quality="medium"
                     nearFiltering="false"
                     compressed="true"
                     renderFormat="rgba8888" />
           
          <shader name="myShader"
                  uid="4"
                  type="standard"
                  useDiffuseWithTexture="true"
                  transparent="true"
                  renderStyle="fill"
                  flat="true">
                  <ambient red="255"
green="255" blue="255" />
                  <diffuse red="0"
green="255" blue="255" />
                  <specular red="255"
green="255" blue="255" />
                  <emissive red="0"
green="0" blue="0" />
          </shader>

           <w3d path="asteroid2.w3d">
              <model name="sphere01"
uid="5"/>
              <shader name="01 - default"
uid="6"/>
              <texture name="asteroid_texture"
uid="7"/>
           </w3d>

	</threedworld>
</df3diproject>

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

For once I can help 

timeout().new("name", intInterval, symHandler,
(,optObjRef))

not sure what happened to your doc, in mine it says :

-- Lingo syntax when scriptExecutionStyle is set to 9
variableName = timeout(name).new(timeoutPeriod,
timeoutHandler, targetObject)

-- Lingo syntax when scriptExecutionStyle is set to 10
variableName = timeout().new(timeoutName, timeoutPeriod,
timeoutHandler,
targetObject)
variableName = new timeout(timeoutName, timeoutPeriod,
timeoutHandler,
targetObject)

cheers,

Matse

Selon Allen R Partridge <allen.partridgeiup.edu>:

> I wouldn't care if someone would just update the docs
to reflect new 
> syntax rules - Come on!
> 
> Ok, so does anyone know the new syntax for using a
timeout object in 
> MX04?
> 
> It was
> 
> timeout("name").new(intInterval, symHandler
{,optObjRef})
> 
> now it is...?


_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

I shall tell you JUST HOW MUCH THIS SUCKS.

I shall.

Yesterday, my coworker stated "dude, your stuff doesn't
work.  It  
worked Friday but it doesn't work now."

So I tried it on my Quad.  It worked.

I tried it on my XP Media Center.  It worked.

We tried it on his box XP media center.  No worky.

He rebooted.

No worky.

I said "Let me to walk through the code and figger it
out yor you, I  
don't want you wasting any more time."

So walking through the code, I find my case statement for
switching  
timeOut syntaxes if you are in Director 9 or Director 10.

See, this inherently SUCKS because I think in terms of
English, not  
TimeOut(Bracket squiggle, squiggle, bracket Paren, Walter
Tango Foxhole

The root of the problem is these differing timeout syntaxes
in each  
version.  Which one do I use?  Every time I come back to
timeouts, I  
have to look up the proper syntax to use and think IT SHOULD
NOT BE  
THIS HARD.  I'm going to have to write a simple time out
wrapper  
handler that I SHOULD NOT HAVE TO DO to take care of this.

This is what I have in all the routines in my libraries
where I  
require timeouts

   myDirectorVersion = Integer(value(the
environment.ProductVersion))
     case ( myDirectorVersion) of
       09:  pTimeoutObj = Timeout( pTimeoutName ).new 
(pServiceInterval, #Service, me)
       10 : pTimeoutObj = timeOut().new( pTimeoutName,
integer 
(pServiceInterval), #Service, me)
     end case

BUT WAIT!  The latest Director version on Windows is not
"10.1" but  
"10.1.1" which does NOT evaluate to an integer,
thereby making  
myDirectorVersion = #Void when run on that version of
Director.

Greeeaat.

So now, the above routine which USED to be just one line of
code  
needs to expand if I am to expect my libraries to run on all
the  
versions of Director I may be coding on:

     oldDelimiter = the itemDelimiter
     the itemDelimiter = "."
     myDirectorVersion = Integer(value((the  
environment.ProductVersion).item[1]))
     case ( myDirectorVersion) of
       09:  pTimeoutObj = Timeout( pTimeoutName ).new 
(pServiceInterval, #Service, me)
       10 : pTimeoutObj = timeOut().new( pTimeoutName,
integer 
(pServiceInterval), #Service, me)
     end case
     the itemDelimiter =   oldDelimiter


Can you say ARGH!

I can.

ARGH!

There, I said it.

and I need to go through all my routines where a timeout may
be and  
fix this.

Hell, I already had to wrote a wrapper for Forget Timeout
that  
doesn't error out  if the time out doesn't exist, looks like
I now  
have to do the same to create a timeout.

Hell, next, I'll have to write a wrapper to open a window to
get it  
to work like it did back in Director 4 where it was EASY.

THINGS SHOULD NOT BE THIS HARD!  That was the beauty of
Director.   
Once, a long long time ago, in a galaxy far far away.

Argle.

The Beauty of Director is that the creative person who did
not think  
in code COULD CODE because verbose Lingo was close to
English,  
therefore making it approachable.  Obviously, I fall on that
side of  
the creative spectrum.  Squiggle, paren, bracket semicolon
makes me  
want to throw up.

Verbose Lingo is EASY.  We NEED EASY verbose equivalents for
 
everything in Lingo.

- Zavaroni

On Nov 21, 2006, at 9:59 AM, Allen R Partridge wrote:

> I wouldn't care if someone would just update the docs
to reflect  
> new syntax rules - Come on!
>
> Ok, so does anyone know the new syntax for using a
timeout object  
> in MX04?
>
> It was
>
> timeout("name").new(intInterval, symHandler
{,optObjRef})
>
> now it is...?
>
> --al
> _______________________________________________
> dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

- Zav
http://goat
s.com/store/zoom/internet.html

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

On 21/11/06 10:59 am, "Allen R Partridge"
<allen.partridgeiup.edu> wrote:
> I wouldn't care if someone would just update the docs
to reflect new
> syntax rules - Come on!
> 
> Ok, so does anyone know the new syntax for using a
timeout object in
> MX04?
> 
> It was
> 
> timeout("name").new(intInterval, symHandler
{,optObjRef})
> 
> now it is...?

Hi Al,

I use a script named "MX 2004 Conversion Broker",
which you can find in the
cast of the movie at <http://nonlinear.openspark.com/tips/oop/scrollBar/>.

This is intended to allow you to make cross-version calls to
create
timeOuts, open windows and other stuff, even if you don't
know which player
will be used to play back your movie.

Cheers,

James

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Reading this thread reiminded me why I ended up doing my own
basic timeout:

--spawn obj
pTimer = script("timer").new(500,me,#someHandler)


--"timer" parent script
property pStartMS, pElapsedMS, pMaxMS
property pCallbackObj, pCallbackHandler

on new me, maxMS, callBackObj, callbackHandler
   pMaxMS = maxMS
   if not(objectP(callBackObj)) then alert("Timer
parent needs the 
object parameter for the callBack")
   pCallbackObj = callBackObj
   if not(symbolp(callbackHandler)) then callbackHandler = 
symbol(callbackHandler)
   if not(pCallbackObj.handler(callbackHandler)) then alert
("Timer 
parent needs an existing callback handler as
parameter")
   pCallbackHandler = callbackHandler
   (the actorList).add(me)
   return me
end

on stepFrame me
   if voidP(pStartMS) then pStartMS = the milliseconds
   pElapsedMS = the milliseconds - pStartMS
   if pElapsedMS >= pMaxMS then
     pStartMS = void
     call(pCallbackHandler,pCallbackObj)
   end if
end

on kill me
   (the actorList).deleteOne(me)
   return VOID
end

-- 
Agustín María Rodríguez

www.onwine.com.ar > Macromedia Director demos & code

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Zav,  I agree with your sentiments that it should be easy to
use. I hated
copypixels when i first started using it. I had to look up
it up many, many
times and I cringed every time I went to use it. I remember
having problems
with Timeouts when I first started using Director, and as a
result, I've
never used them.

However, what you say about verbose lingo being EASY is
simply not true for
everyone. Verbose is easy for you, arguably because you've
been using it for
10 years (or however long it's been). But if someone doesn't
know the proper
syntax for verbose lingo, then it's just as confusing, if
not moreso,
because it's so non-standard. I've always had problems with
Verbose, and
understanding how to use it. I think Director should be
EASY, but I don't
think EASY = VERBOSE and vice versa.  What is the verbose
version of
copypixels (if there is one) ? If there isn't, what would
you propose it be?

Hanford

On 11/21/06, Alex Zavatone <zavpublicmac.com> wrote:
>
> I shall tell you JUST HOW MUCH THIS SUCKS.
>
> I shall.
>
> Yesterday, my coworker stated "dude, your stuff
doesn't work.  It
> worked Friday but it doesn't work now."
>
> So I tried it on my Quad.  It worked.
>
> I tried it on my XP Media Center.  It worked.
>
> We tried it on his box XP media center.  No worky.
>
> He rebooted.
>
> No worky.
>
> I said "Let me to walk through the code and figger
it out yor you, I
> don't want you wasting any more time."
>
> So walking through the code, I find my case statement
for switching
> timeOut syntaxes if you are in Director 9 or Director
10.
>
> See, this inherently SUCKS because I think in terms of
English, not
> TimeOut(Bracket squiggle, squiggle, bracket Paren,
Walter Tango Foxhole
>
> The root of the problem is these differing timeout
syntaxes in each
> version.  Which one do I use?  Every time I come back
to timeouts, I
> have to look up the proper syntax to use and think IT
SHOULD NOT BE
> THIS HARD.  I'm going to have to write a simple time
out wrapper
> handler that I SHOULD NOT HAVE TO DO to take care of
this.
>
> This is what I have in all the routines in my libraries
where I
> require timeouts
>
>    myDirectorVersion = Integer(value(the
environment.ProductVersion))
>      case ( myDirectorVersion) of
>        09:  pTimeoutObj = Timeout( pTimeoutName ).new
> (pServiceInterval, #Service, me)
>        10 : pTimeoutObj = timeOut().new( pTimeoutName,
integer
> (pServiceInterval), #Service, me)
>      end case
>
> BUT WAIT!  The latest Director version on Windows is
not "10.1" but
> "10.1.1" which does NOT evaluate to an
integer, thereby making
> myDirectorVersion = #Void when run on that version of
Director.
>
> Greeeaat.
>
> So now, the above routine which USED to be just one
line of code
> needs to expand if I am to expect my libraries to run
on all the
> versions of Director I may be coding on:
>
>      oldDelimiter = the itemDelimiter
>      the itemDelimiter = "."
>      myDirectorVersion = Integer(value((the
> environment.ProductVersion).item[1]))
>      case ( myDirectorVersion) of
>        09:  pTimeoutObj = Timeout( pTimeoutName ).new
> (pServiceInterval, #Service, me)
>        10 : pTimeoutObj = timeOut().new( pTimeoutName,
integer
> (pServiceInterval), #Service, me)
>      end case
>      the itemDelimiter =   oldDelimiter
>
>
> Can you say ARGH!
>
> I can.
>
> ARGH!
>
> There, I said it.
>
> and I need to go through all my routines where a
timeout may be and
> fix this.
>
> Hell, I already had to wrote a wrapper for Forget
Timeout that
> doesn't error out  if the time out doesn't exist, looks
like I now
> have to do the same to create a timeout.
>
> Hell, next, I'll have to write a wrapper to open a
window to get it
> to work like it did back in Director 4 where it was
EASY.
>
> THINGS SHOULD NOT BE THIS HARD!  That was the beauty of
Director.
> Once, a long long time ago, in a galaxy far far away.
>
> Argle.
>
> The Beauty of Director is that the creative person who
did not think
> in code COULD CODE because verbose Lingo was close to
English,
> therefore making it approachable.  Obviously, I fall on
that side of
> the creative spectrum.  Squiggle, paren, bracket
semicolon makes me
> want to throw up.
>
> Verbose Lingo is EASY.  We NEED EASY verbose
equivalents for
> everything in Lingo.
>
> - Zavaroni
>
> On Nov 21, 2006, at 9:59 AM, Allen R Partridge wrote:
>
> > I wouldn't care if someone would just update the
docs to reflect
> > new syntax rules - Come on!
> >
> > Ok, so does anyone know the new syntax for using a
timeout object
> > in MX04?
> >
> > It was
> >
> > timeout("name").new(intInterval,
symHandler {,optObjRef})
> >
> > now it is...?
> >
> > --al
> > _______________________________________________
> > dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
> > http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
>
> - Zav
> http://goat
s.com/store/zoom/internet.html
>
> _______________________________________________
> dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
>
_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l