[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rescheduling
From: |
Marcus G. Daniels |
Subject: |
Re: rescheduling |
Date: |
Wed, 21 Apr 1999 17:24:52 -0600 (MDT) |
KC> Does this `respondsTo' test work for all actions scheduled for a
KC> particular target object?
It's like doing a isKindOfClassNamed: "ActionTo_0"; ActionTo is the
only Action that responds to the -getTarget method..
KC> What if the actions were put into an
KC> ActionGroup and then the entire ActionGroup was scheduled?
The code would be inadequate for that.
KC> Is this what you meant by a "Conservative use of remove:"?
Heh, yes.
KC> BTW, do ActionGroups stay "grouped" after they are scheduled?
Yes.
MD> [schedule remove: action];
KC> Does the `remove:' message to a Schedule drop the action?
No, it's like a remove in a Collection.
KC> How about its associated key (i.e. timeval_t); does that
KC> memory need to be freed as well?
The key will be freed.
KC> Is it safe to just drop
KC> and action (and its key); are we sure its not on multiple
KC> schedules?
Well, in principle, Actions are different things from Schedules, so
you shouldn't count on an Action not being on multiple Schedules. As
a practical matter Actions are typically created on behalf of a method
like Schedule's at:createActionTo:message: (further, if you have the
AutoDrop feature set that kind of one-to-one relationship is implied).
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.