passing arrays as parameters

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/04/2012 at 02:37, xxxxxxxx wrote:

uh i made a mis take in my example, when i shortend the code, it has to be

static BaseObject * ~~Opolylight::~~ GetPlane(BaseObject *op)
    
    {
    
    	BaseObject *result = NULL;
    
    	result = BaseObject::Alloc(Oplane);
    
      
    
    
    	BaseContainer *outbc = result->GetDataInstance();
    
    	BaseContainer *inbc = op->GetDataInstance();
    
      
    
    
    	...
    
    	return result;
    
    }

of course.

  


@ nikklas

  


i am not talking about GetVirtualObjects, it is called on each update and there are examples in 

the sdk how to treat cases in which GetVirtualObject fails to produce a propper output (free

the memory).

  


but i have firgured it out somehow i guess, i have just to create some kind of garbagecollector 

method which clears all the unused static pointer method adresses. i'll report back when i fail again :)

  


ps : refusing to praise & and use microsoft products is considered to be a mortal sin by the spanish

inquisition.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/04/2012 at 05:27, xxxxxxxx wrote:

Whatever object you return in GetVirtualObjects(), don't care about its memory anymore. Cinema takes over the ownership.

If you allocate an object but don't return it at the end of GetVirtualObjects(), you have to free it yourself of course.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/04/2012 at 08:44, xxxxxxxx wrote:

hi,

and here i am again, i tried to check my code so i placed a c4d_debug.txt in my c4d folder.
first i started c4d from the desktop and the console window said meh, debugger not present
so i started c4d from vs using my project (which compiles and runs fine atm), c4d crashes again
with the exception floating point division by zero. so i tried the sdk_examples with the 32 bit debug
platform. it starts without any errors, but the console doesn't show up, not while debugging, not after.

i am on vista 64 bit, c4d demo 32 bit and VS 8.0.5

has someone experience with this odd behaviour ?

sorry, for throwing random questions at you

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/04/2012 at 22:05, xxxxxxxx wrote:

for the Console to show up you need to set the startup directory in VS to the c4d folder (project properties -> debugging). Else it won't find the c4d_debug.txt
or you put the c4d_debug.txt in the plugin's folder

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/04/2012 at 01:29, xxxxxxxx wrote:

Originally posted by xxxxxxxx

so i placed a c4d_debug.txt in my c4d folder.

Already said, that text file better goes into your plugin's folder. Otherwise, Cinema will do the memory trace everytime your start it, and that is usually not desired.

Originally posted by xxxxxxxx

i started c4d from vs using my project (which compiles and runs fine atm)

That's the right way to do. Create a Debug build in VS and use the "Play" button to start Cinema in the VS Debugger.

Originally posted by xxxxxxxx

c4d crashes again with the exception floating point division by zero.
so i tried the sdk_examples with the 32 bit debug
platform. it starts without any errors

Then the DivByZero is definitely a bug in your code ALWAYS check for zero before doing any division (or take care that zero will never occur).

Originally posted by xxxxxxxx

sorry, for throwing random questions at you

That's OK, but I really think you should open separate threads for separate questions. That way, it will be much easier for other people to find your questions and the answers.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 26/04/2012 at 18:40, xxxxxxxx wrote:

Yes, I already said this. An argument will be put into a CPU register if available otherwise it goes onto the stack. This is why four or less arguments for a method are faster. As someone with nearly 30 years of programming and most of that using C/C++, I definitely know what the hell I'm talking about.

http://msdn.microsoft.com/en-us/library/zthk2dkh%28v=vs.80%29.aspx