New class in script?

#1 Did I stump everyone?

#2 Try changing your SimObject name to something other than your class name (so that they are not the same). Also make sure that your functions are defined before they are used.

#3 Tried that... still didnt work.

heres what I had:

function ClientPlayer::initData()
  {
   echo("initData called");
  }

function ClientPLayer::ReRoll()
  {
   echo("ReRoll called");
  }

function CharacterCreatorGui::onWake(%this)
  {
   $NewPlayer = new SimObject(ClientPlayer1)
     {
      class = ClientPlayer;
     };

   $NewPlayer.initData();
   $NewPlayer.ReRoll();
    }

instead of getting "initData called" and "ReRoll called" in the console I get the same 2 errors above:
Unknown command initData.

one thing that still hasnt been answered is weather or not I can even DO this.. say nothing if im doing it right.

#4 Instead, do:

$NewPlayer.getDataBlock().initData();
$NewPlayer.getDataBlock().ReRoll();

#5 That doesnt work either.
now i get this:
==>Canvas.pushDialog(CharacterCreatorGui);
starter.rpg/client/ui/CharacterCreatorGui.gui (712): Unknown command getDataBlock.
Object ClientPlayer(16870) SimObject
starter.rpg/client/ui/CharacterCreatorGui.gui (712): Unable to find object: '' attempting to call function 'initData'


replacing getDataBlock() with dataBlock gives this error:
starter.rpg/client/ui/CharacterCreatorGui.gui (712): Unable to find object: '' attempting to call function 'initData'

any more suggestions?

#6 Try changing

%NewPlayer = new SimObject(ClientPlayer1)
     {
      class = ClientPlayer;
     };

to

%NewPlayer = new ScriptObject(ClientPlayer1)
     {
      class = ClientPlayer;
     };

#7 Using ScriptObject seems to have solved my problems.

Thanks matt!

#8 For those that may follow along on this discussion, the reason ScriptObject works when "normal" objects don't is a design decision:

Originally, TGE was built with the concept that everyone would always implement a new c++ class for their objects, and simply use TorqueScript to manipulate those objects. Namespace linking was designed such that whenever you called a method on a Torque Object, the scripting system would search the namespaces associated with the inheritence tree of the c++ class.

Now, in some cases, it does make sense to have some basic namespace classing system in TorqueScript, but it is important to note: TorqueScript is not fully Object Oriented. We fake some things with special classes of objects to give some "oop-ness", but in general if you want full oop, you should create new c++ classes.

In stock TGE, any script object instantiated from a GuiObject, or a ScriptObject, will allow you to use the "class" and "superclass" persistent fields to link additional namespaces--as well as a namespace for the instantiation's unique nae (ClientPlayer1 in the above example), but this does not apply for all object types.

#9 Thanks for the summary.
creating a myrad of C++ classes is exactly what im trying to avoid. im not looking for any of the advanced OO concepts here - simple inheritance and method override will work fine.

Although if there was a java or Smalltalk interface to torque - that would be a different ballgame.