node movement (Part 1)

---

The first thing we're going to modify is the pacman.py file. We need to pass in the list of nodes that make up the maze. Instead of specifying a random pixel position vector for Pacman to start out on we need to tell him which node we want him to start out on. Right now it doesn't matter so we'll just have him start out on the first node, so we set his position to be the same as that nodes position. So nodes is the NodeGroup class and node is the node that Pacman is currently on. Then we call a method called setPosition. 

We need to create a new method in the Pacman class. All this method really does is copy the node's position to Pacman's position. We call the copy method because we don't want the same position object associated with Pacman and the node. If it is then modifying Pacman's position will also modify the nodes position. The node will basically follow Pacman around. So instead we copy the position which gives us a fresh new vector to represent Pacman's position. 

We need to modify Pacman's update method. In the update method we're going to temporarily comment out the position update.  Don't delete it, just comment it out for now.  This is only temporary to show you this type of movement though. We also remove the else condition since we don't make Pacman stop based on key presses. From here on out we'll make him stop via conditions in the code.

The other two new methods,  validDirection and getNewTarget, checks whether the key we're pressing is a valid direction and whether there is a node in that direction.  If so, then we move Pacman to that node automatically.

 In the run.py file we're going to modify the startGame method so that we pass in the node we want Pacman to start on.  The first node in the list is as good as any for the time being.