Re: getCurrentTime

[Sven Thommesen]

At 10:36 PM 3/27/97 -0700, glen e. p. ropella wrote:
>
>So, have you tried using the normal Objective C way of 
>getting data out of the activity object? ....i.e. by 
>sending it a message?  I don't see the need for the 
>macro in the first place.
>
>glen
>

I will in a minute -- seems I don't have much choice!
Your less-terse explanation made some sense (more than
your previously very terse one, anyway!)

But I'd have greatly preferred if existing code hadn't
gotten broken like this -- why not have those messages,
which the macro evidently actually calls, return t=0
or t=-1 or somesuch if an activity is not activated,
rather than the brutal 'InvalidCombination raiseEvent'?

(I'd also point out that this little item doesn't seem
to have made it into the docs re: incompatibilities.)

So, let me see, I'm making these macro calls before
saying 'go' -- what activity object should I send 
messages to? [Think Heatbugs here.]

And and what will the likely result be ... ?

As for relativity and religion -- no, I don't mind at all!
Always a joy to have a little repartee with interesting
and/or intelligent people out there. That's a major benefit
of the Internet! Despite being religiously challenged,
I think I can take a reference or two to God without having
a fit. And we all know the Centauri are swell people, unless
you ask the Narn of course :-)

And as for time being relative within my own simulation, that'll
require some serious head time ... 

-Sven