Re: Argument passing in Schedule

[Ho-Sheng Hsiao]

On Mon, 10 Feb 1997 address@hidden wrote:
> Minor point - that last line should read 
> 
>     return [self getActivity];

I really wonder how I get the thing compiled ... I think I typed it out
from memory. (I just double checked, and it is the same, sans comment).

> This is only important if you later make use of that returned
> value for activity....however, if the modelSchedule is working
> and the modelScratchSchedule is not, this ain't the problem....

modelScratchSchedule works *if* I put in a message before it was
activated... but I tried adding an action to modelScratchSchedule
*immediatly* after it is activated -- that works, but for another object,
and not the one I want to send to. 

*sigh* I'm going to look further into why one object class works, and
another doesn't. (Both doesn't work under modelDeliverRouterMessage, the
exact place I *do* want it to work).


---hhh