Chaos Project

Featured Projects => Tasks => Advanced RPG Creator => Finished Tasks => Topic started by: Blizzard on March 27, 2011, 06:12:17 am

Title: [Finished] [RGSS] Fix Incorrect Definitions
Post by: Blizzard on March 27, 2011, 06:12:17 am
Fix Incorrect Definitions




Description

While going through our current code, I have noticed that quite a few classes where the interface was not implemented properly. I have see a few methods where the parameter number is incorrect and I have noticed that some methods don't return the proper value. Make sure that:





Priority

High.



Prerequisites

Ruby/C++ Interfaces (http://forum.chaos-project.com/index.php/topic,8982.0.html) (finished)



Assigned

ForeverZer0



Everything else

Double check if everything is ok. Double checking is pretty much what this task is.
Title: Re: Fix Incorrect Definitions
Post by: G_G on March 28, 2011, 09:08:36 am
I'll take this on.
Title: Re: Fix Incorrect Definitions
Post by: Blizzard on April 08, 2011, 05:33:13 am
You can finish this task now. It should be fairly easy.
Title: Re: Fix Incorrect Definitions
Post by: Blizzard on April 15, 2011, 05:10:13 pm
F0, I am reassigning this task to you.
Title: Re: Fix Incorrect Definitions
Post by: ForeverZer0 on April 15, 2011, 06:31:47 pm
On it.

EDIT:
One quick question before I get too far ahead of myself.
I know to leave the names for single arguments as "value" for setters, but can I explain a little better in the definition what that "value" is?

example from Color:
      /// @brief Sets the font's name.
      /// @param[in] String Default name of the font.
      static VALUE rb_setDefaultName(VALUE classe, VALUE value);
Title: Re: Fix Incorrect Definitions
Post by: Blizzard on April 17, 2011, 03:42:34 pm
This:

      /// @brief Sets the font's name.
      /// @param[in] value Default name of the font.
      static VALUE rb_setDefaultName(VALUE classe, VALUE value);

We omit the classe argument and the self argument because they are Ruby specific implementations.
Title: Re: Fix Incorrect Definitions
Post by: ForeverZer0 on April 17, 2011, 03:46:48 pm
Alrighty, just making sure.
I should have it committed by the end of the night. I have a little running around to do, then I'm gonna finish it before I go to bed.
Title: Re: Fix Incorrect Definitions
Post by: Blizzard on April 17, 2011, 03:47:56 pm
Sounds good.
When you're done and after you have double checked everything, feel free to mark this task as completed and move it into the section for completed tasks.
Title: Re: Fix Incorrect Definitions
Post by: ForeverZer0 on April 20, 2011, 12:00:30 am
Committed.
There are a couple minor things I cannot change as of yet, do to being incomplete.



* Marks as finished and moves *
Title: Re: [Finished] Fix Incorrect Definitions
Post by: Blizzard on April 20, 2011, 02:28:47 am
Don't worry about it. You did your task, I'll take care of the rest. xD
BTW, what do you mean with Plane? As far as I remember, you have to pass a viewport as argument. Or did you mean that is should have a C++ constructor?
Title: Re: [Finished] Fix Incorrect Definitions
Post by: ForeverZer0 on April 20, 2011, 02:32:31 am
I thought the viewport was optional, like how Sprite is, if I am remembering correctly. I could be wrong.
Currently the C++ code has no way to handle the class being instantized without a viewport passed.

* Goes to check it out

EDIT:

* Returns...

Yeah, it should be able to be called without no argument.
Title: Re: [Finished] Fix Incorrect Definitions
Post by: Blizzard on April 20, 2011, 02:50:28 am
That's weird. How is it supposed to be drawn? Can you check out how it works in RMXP if you don't give it a Viewport?
Title: Re: [Finished] Fix Incorrect Definitions
Post by: ForeverZer0 on April 20, 2011, 02:52:43 am
Will do, but I am going to bed now. It is late-as-hell-o'clock where I am, and I have work in the morning. :'(
Title: Re: [Finished] Fix Incorrect Definitions
Post by: Ryex on April 20, 2011, 03:00:47 am
as I understood it it works exactly like sprite dose If you don't give it a viewport.