Defining data structures in script?

#1 Hola David,

Could you post a snippet of what you have been trying?

-Josh

#2 I've been through several iterations using ScriptObject and DataBlock.

This is the current failure:

datablock GameBaseData(PrivateMessageItem)
   {
   Sender = 0;
   Message = "";
   };

datablock GameBaseData(PrivateMessageVector)
   {
   PMCount=0;
   PMVector = 0;
   };
   
function PrivateMessageVector::AddPM(%this,%sender,%message)
   {
   %this.PMVector[%this.PMCount]=new PrivateMessageItem();
   %this.PMVector[%this.PMCount].Sender=%sender;
   %this.PMVector[%this.PMCount].Message=%message;
   %this.PMCount++;
   }

readyRoomPrivateMessageVector=new PrivateMessageVector();

The error I get is on the attempt to create an instance of PrivateMessageVector.

That's actually where I've received the error for each attempt, even when I was using ScriptObject-based structures. In that case, the error was "attempting to instantiate a non-conobject" or something like that.

Thanks.

-David

#3 This only my second day with Torque scripting... but I believe you have to do the following:

$readyRoomPrivateMessageVector= new GameBaseData() {
datablock=PrivateMessageVector;
};

-J

#4 The below compiles and appears to run for me, I don't know that the script language has a concept of creating new classes... notice the term datablock... I believe you can add functions to native cpp classes exposed to the script engine... but I don't think you can add a class in script itself.. I could be wrong...

datablock GameBaseData(PrivateMessageItem)
{
Sender = 0;
Message = "";
};

datablock GameBaseData(PrivateMessageVector)
{
PMCount=0;
PMVector = 0;
};

function PrivateMessageVector::AddPM(%this,%sender,%message)
{
%this.PMVector[%this.PMCount]=new GameBaseData(){
datablock=PrivateMessageItem;
};

%this.PMVector[%this.PMCount].Sender=%sender;
%this.PMVector[%this.PMCount].Message=%message;
%this.PMCount++;
}

$readyRoomPrivateMessageVector=new GameBaseData()
{
datablock=PrivateMessageVector;
};


PrivateMessageVector::AddPM($readyRoomPrivateMessageVector,$readyRoomPrivateMessageVector,"hey");

#5 That *is* compiling now, and even looks like it should do what it's supposed to. I'll be testing the whole thing later today. I'll report back how it goes...

Thanks alot!

-David
Samu Games

#6 I am almost certain there would be another (better?) way of doing this... this resource could help: www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=2212

Also in digging thru some sample sources I noticed a className field which should work like inheritance...

I think I may pick thru Tribes2 scripts for some ideas... so far I like the scripting...

The process of discovery... currently I am trying figure out how I could call that PMAdd function without the namespace qualifier... I would think there would be some kind of syntax fixup which would allow you to use the obj.function() notation... I am probably just missing something...

-J

#7 The datablockname::functionName does allow you to use the dot-notation: %obj.functionName

The name of the object becomes the namespace. Sorta.

Thanks again!

-David

#8 I can declare either with:

function GameBaseData::AddPM(%this,%sender,%message)

or

function GameBaseData::PrivateMessageVector::AddPM(%this,%sender,%message)

If this is the way to do it, I would guess that the second is preferable to avoid namespace pollution?
Declaring with:

function PrivateMessageVector::AddPM(%this,%sender,%message)

causes the function not to be found with the %obj.function() notation.. I have to use the fully qualified PrivateMessageVector::AddPM(this,that,msg)


-J

#9 Duh:

$readyRoomPrivateMessageVector=new GameBaseData(PrivateMessageVector);

And voila... I like it!

-J

#10 I've had good luck doing classes in this wise:

$classInstance = new ScriptObject() {
class = foo;
}

function foo::testIt(%this, %a) {
echo ("I am testing, " @ %a);
}

$classInstance.testIt("you!");

Outputs:

I am testing, you!