11 Comments

1. 

   Nosakos on January 19, 2012 at 2:36 pm

   Thanks mike for your vids, I love them!
   But i have a question. Why do you use the init function instead of a second constructor that initializes the attributes of the class.

   Reply
   • 

     Mike on January 19, 2012 at 2:42 pm

     A second constructor would have required me to rebuilt the object as a brand new object. I could have deleted the old object and then set the new one, but I would have had to pass in the image again anyway as it would not have remembered the image from the previous object.

     Reply
     • 

       Nosakos on January 19, 2012 at 3:51 pm

       Thanks for your answer.
       All i wanted to say is that we would use only one constractor that would also initialize the attributes with the one given by us.

       Reply
2. 

   Nosakos on January 20, 2012 at 5:51 pm

   Nevermind, after watching your vid for a second time, i found out that at start we cant load the image so thats why we use the init.

   Reply
3. 

   Neon on July 28, 2012 at 6:45 pm

   Hi:

   One Question: Why don’t use the function “void GameObject::Init (…)” to init maxFrame, curFrame, frameWidth, frameHeight, etc.

   This variables belong to Ship, Bullet and Comet, can init in mother class (class GameObject).

   Sorry my english :S, i’m from Spain. Thanks.

   Reply
   • 

     Mike on July 31, 2012 at 11:16 pm

     I’m not sure what you are asking. Since they are different from each other, they have to be initialized in their own classes

     Reply
     • 

       neon on August 8, 2012 at 1:44 pm

       Ok, I understand. But use the function “Init(…)”, not use the constructor, ¿why?.

       Reply
       • 

         Mike on September 21, 2012 at 3:08 pm

         The constructor is called as soon as the object is made. That happens before Allegro is initialized and will fail. Thus, we use the init method

         Reply
4. 

   Robert on September 19, 2012 at 2:31 pm

   Hey!

   First of all: Thank you very much for your work! I’ve worked through your tutorials and it really got me going! Great stuff!

   But I was wondering about some stuff, regarding your OO tutorial here:

   1. Why do you access your instance veriables through your class name like GameObject::x and not by this->x?
   To me this looks like GameObject was a static class like a singleton, not a simple object class.

   2. I know it’s just for demonstration purposes, but wouldn’t it be “better” to write your constructers the way to use your methods if applicable? Like calling your GameObject::Init() method in your GameObject::GameObject() constructer with zero values. This way if anything changes you just need to update your method and the method call, not the cunstructor as well.

   3. In your cunstructors and Init() methods you should/could use your Set*() methods, for the same reason.

   Is there any reason to not do those things, like performance or so? Would be glad to know then 🙂

   Anyway, keep up the good work and thank you very much!

   Reply
5. 

   Mike on September 21, 2012 at 3:36 pm

   1) You could do it either way.
   2) You are correct, that would be less redundant.
   3) Again you are correct. I thought about doing things like that, but ultimately decided on as much simplicity as possible

   Reply
6. 

   Maciej on November 12, 2012 at 11:32 pm

   ~AAAwesome, It’s exactly what I need at this moment!

   Reply