von DAniel am 22.Dezember 96 um 15:23:11:
zu: actorList manager von Daniel am 22.Dezember 96 um 15:17:47:
Yes, that's why you should only put items on the actor list or your own
internal activeActors list only when they have real tasks to perform. By
only putting objects on the list that are currently animating, you can
target all the processing exactly where it needs to go.
Items that are simply sitting on the screen waiting for mouseclicks should
NOT be sitting on the actorlist. We usually keep them in their own control
lists. We keep a global sprite list and when an object is activated for a
screen control like a button, it puts its pointer into the global sprite
list. Then all mousedown and mouseup messages are passed directly to the
object by indexing into the sprite list. We don't put these types of
objects in the activeActors list.
So I don't necessarily agree that the actorlist (or an internal custom
activeActors List) should be avoided, only that it should be properly
managed and used in conjunction with other control structures. Just don't
try to do everything in the actor list and don't put pointers to items in
the activeActors list that don't currently need to receive stepframes.
-MikeS
D. Plänitz