Michael Bayne
00fde3eeb3
rather than codes to indicate different types of events. Also modified name of sprite observer callback as spriteChanged() implies that the sprite actually changed which it may not have, whereas handleEvent() doesn't imply anything other than the sprite observer is being asked to deal with a sprite event. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@338 542714f4-19e9-0310-aa3c-eee0fc999fb1
33 lines
704 B
Java
33 lines
704 B
Java
//
|
|
// $Id: PathCompletedEvent.java,v 1.1 2001/09/13 19:36:20 mdb Exp $
|
|
|
|
package com.threerings.media.sprite;
|
|
|
|
/**
|
|
* A path completed event is dispatched when a sprite completes a path
|
|
* along which it has been requested to move.
|
|
*/
|
|
public class PathCompletedEvent extends SpriteEvent
|
|
{
|
|
/**
|
|
* Constructs a path completed event for the specified sprite and
|
|
* path.
|
|
*/
|
|
public PathCompletedEvent (Sprite sprite, Path path)
|
|
{
|
|
super(sprite);
|
|
_path = path;
|
|
}
|
|
|
|
/**
|
|
* Returns the path that was just completed.
|
|
*/
|
|
public Path getPath ()
|
|
{
|
|
return _path;
|
|
}
|
|
|
|
/** A reference to the completed path. */
|
|
protected Path _path;
|
|
}
|