BTW I have another question. I'm new to AS3.0, even though I have some good knowledge in AS1.0 The thing is that I'm try hard to learn and apply good programming tecniques, so my question is: is this a good practice? to have different files for different objects in the game? And to declare the global and local vars and function in the way I'm doing it?I believe that, in that way, I wall have better control in programming the game. I'm just having difficult to connect the codes between files.[/quote]

Sometimes this kind of question starts an OOHW (Object-Oriented Holy War) so anything I tell you here is opinion only. In AS3 most (not all, there are some pretty esoteric exceptions that I won't get into) types go into their own file. The way you've set up Main and Mission is good practice. Declaring all your class members public is not good practice though, if you never use mission1Room1 outside your Mission class, it should be private. Public variables in classes should also be treated very carefully. While it's certainly OK to declare public variables (again, my opinion), make sure that changing the values of those variables is safe no matter who does it. Otherwise, crashes and bugs are certainly going to be a big part of your future.

From what I can gather, your class structure does need some work though. Try thinking of the whole scheme like this:

• The game has a set of missions.
  
• Each mission has rooms you can visit.
  
• Each of these rooms may or may not contain one or more objects.
  

Making use of that code, I saw that the first totalObjectsMission1 actually disappear; and now shows the totalObjectsMission1 of the Mission1 function. This is good so far I don’t need to use the constructor code, but what if I do?[/quote]

So this turns out to be a pretty hairy design question in my opinion. I stay clear of public functions (other than maybe the constructor of the class) that change public member variables. What does that mean? Something like this:


public class MyObject {
public var myPublic:int;
private var myPrivate:int;

//Change away here.
public function MyObject()
{
myPublic = 1;
myPrivate = 2;
}

public function doSomething():void
{
myPublic = 4; //This is bad!
myPrivate = 5; //This is OK.
}
}



function someOutsideFunction():void
{
var mine:MyObject = new MyObject();
mine.myPublic = 7;
trace(mine.myPublic); //So far so good, traces 7.
mine.doSomething();
trace(mine.myPublic); //What? I just said you were supposed to be 7, not 4!
}


You should try avoiding situations like that as much as possible.

With this you are saying that (and thinking that class members are all the vars) I have to declare them private?[/quote]

You don't HAVE to. It's just a really good idea to give each variable the lowest level of access to the outside world as possible. So if you only use a variable inside one class, make it private. That way, it can never be changed by some other class accidentally.

If so, this is true; I have seen other codes and I found that actually, they use private vars. You say that this safer, why is that?[/quote]

So this is a really contrived example but:


//MyClass
public myVar:int;

public function myFunction():void
{
if(myVar == 5) {
throw new Exception("myVar isn't supposed to be 5!");
}
}

//Later...

function causeTrouble():void
{
var myClass:MyClass = new MyClass();
myClass.myVar = 5;
myClass.myFunction();
}


You're never going to intentionally write code like that, but you may write something similar accidentally. Having private variables helps you avoid that.

- Well at first sight I say WOW, looks very clean and awesome. The thing is that, for example, all the missions (inside every room) will have an array of inventory objects [scissors, paper, scanner and so on (up to 4)]. I already successfully make that those objects to be left over the objects inside every room. For the objects in the room I declared another array that has all the objects in the room. Now, I made a for that finds all the objects in the inventory (objectsInv) and created a listener that listens when that object is click. If it does, stratDrag(). If it doesn’t (this is the tricky part) I declared a for that reads all the objects in the scene (mission1Objects[j]) and, if event.currentTarget.hitTestObject(mission1Objects [j]) remove listener, if it doesn’t, you inventory object go to your initial place. (Please tell me if I made myself clear)
The question is, how can I handle this? Thinking a little more, I can import the Inventory file to the Missions file, maybe? But that Inventory will interact too with a small store, so this is where I get a little confused, what do you think?[/quote]

So each room has a set of objects you need to use in it? Hopefully I understood that correctly or this might not make any sense:

What it seems you have is a bunch of keys that fit into a bunch of locks. For example, a pair of scissors (the key) fits into a sheet of paper (the lock). When that happens the paper gets cut (or whatever else). So maybe your setup works something like this:

• Each room has a set of locks, all these locks are paired with a key (a unique identifier shared by both keys and locks, like a unique number or string).
  
• Each room can also have keys inside it that you can pick up and add to your inventory.
  
• Whenever you click and drag a key to a lock, something happens.
  

for example the missions, it's better to have each function separately? away from constructor? With each one having it's own vars?[/quote]

If it were me I'd most likely make a mission class like you have, and have each room maintain a mission. All missions will most likely work roughly the same way, they'll all start, and they'll all end. They all have goals (place the teddy bear on the table, etc.). If any of them behave differently, you can make a specialized type of mission by inheriting from the basic mission type (like you were inheriting from MovieClip for Main). Then each one will have its own copy of mission variables that you can set to default values in your constructor.

With this in mind, how can I make interact both inventory objects and game objects? So far, I have them in the same file and works great. But thinking in using better programming techniques? I thought about:
1) Create another file (for example InventoryGameInteraction) that imports and uses both inventory objects and game objects.
2) Import the game objects to the inventory objects and use them from there.
What do you think?[/quote]

I like the first option simply because it makes more sense to think about in a non-programming way. What I mean by that is: I tend to think about problems in terms of real-world objects. So, locks and keys, or rooms and missions. Consider: You walk into a room and in your pockets are a few items you're have to put in that room. What are you going to use to actually place them? The second option basically says you'd use your pocket to place them. The first option is easier to think about if you think of it as a "hand" that's taking something out of your pocket (inventory) and placing it in the room.