1. Added more to the objHolderArr, so it is a three row/six column grid. This is a visual gird that is easier for us visual people to understand.

2. Added the button into the ball Object with the dispatch event code, this is really the best way to handle the click.

3. Added some score code and the code to remove the ball when it is clicked. It is now almost a fully functioning game.

You will notice that code to remove the ball is almost an exact copy of most of the code from the activeChecker function. Normally I would make a new function with just the code that is the same and call it from both places. this will help if there is a bug or an update to keep the code clean. Again, this is nice to have, a best practice but will not make or break the game.

I know, just get it to work for now, you can clean up the code later, nuff said.
Good luck.

The configuration code works for this sample and may not work for your game, but the concept is still valid. The idea is to have controls built into your code, so that you can tweak things during testing. A simple example would be a speed variable.

Say you test the game and it is too fast or too slow, instead of searching through the code and finding all the places that you hard coded the speed, you could have one speed variable. By changing one number, you can effect how the game plays until it feels right. As the games get more complex, you can add more configuration hooks into your code. But do not let this hold you up. It does not stop the game from working, it is a good practice, but not essential.

In the sample, I can add remove, objects, changes scores, control how long they stay on screen all in the config section of the code. try messing with the delay and timeInc variables.

For the clicking event. In this example code you could add it into this area

//******* add code here to initiate your visual objects.
var tempBO:ballObj = new ballObj();
tempBO.x = slotObj.xCoor;
tempBO.y = 20;
tempBO.objIDStr = arrLoc.toString();
tempBO.objScoreStr = levelArr[arrLoc].score;
tempBO.objTypeStr = levelArr[arrLoc].obj;
addChild(tempBO);

just add a line.
tempBO.addEventListener(MouseEvent.CLICK, clickHandler);

Then add a function called clickhandler.
function clickhandler(ev:MosueEvent)
{
//handle click event
}

If there are issues with the click event not firing consistently when clicking on the bug, then you may need to add a button into the Ball Object (action script file),
(You will have to import any classes for the button or SimpleButton) Add an event listener to the button, then in the handler add this line. dispatchEvent(new Event(“BUG_EVENT”,true);

Then back in the fla add a listener, addEventListener(“BUG_EVENT”,bugHandler); then add a function called bugHandler,

Sorry if I am throwing too much info at you each time, if you need more specific answers it really helps to see some code or have more details for the game play. If you want to share that with me offline, use the contact link at that top of the page and I will get back to you through email.