Forums > Dev

compiled objects appear with no inlets/outlets

March 2, 2007 | 12:26 am

Hi,

thanks for all the help from everyone so far, I am now facing my next problem, that the recompiled objects from the SDK tutorial load without errors, but with no inlets or outlets, the same way it would if I just typed any random letters or numbers into an object box.

Is there anything obvious I’m overlooking?

Thanks again


March 2, 2007 | 2:39 am

Do you mean it’s a bogus object? Are there error messages in the Max Window?

wes

On 3/1/07, Kieran Coulter wrote:
>
> Hi,
>
> thanks for all the help from everyone so far, I am now facing my next problem, that the recompiled objects from the SDK tutorial load without errors, but with no inlets or outlets, the same way it would if I just typed any random letters or numbers into an object box.
>
> Is there anything obvious I’m overlooking?
>
> Thanks again
>
>
>


March 2, 2007 | 2:48 am

I am assuming Max can find the object, if it can not it will tell you
in the Max window. I did run into a similar problem where Max
does not like it when the name of the object does match the
file name. They have to match exactly.

Anthony

—– Original Message —–
From: "Wesley Smith"
To:
Sent: Thursday, March 01, 2007 8:39 PM
Subject: Re: [dev] compiled objects appear with no inlets/outlets

> Do you mean it’s a bogus object? Are there error messages in the Max
Window?
>
> wes
>
> On 3/1/07, Kieran Coulter wrote:
> >
> > Hi,
> >
> > thanks for all the help from everyone so far, I am now facing my next
problem, that the recompiled objects from the SDK tutorial load without
errors, but with no inlets or outlets, the same way it would if I just typed
any random letters or numbers into an object box.
> >
> > Is there anything obvious I’m overlooking?
> >
> > Thanks again
> >
> >
> >


October 25, 2012 | 6:03 pm

just to follow up. If you ever lack inlets on an object, check the line

c = class_new("ar_object~", (method)ar_object_new, (method)dsp_free, (long)sizeof(t_ar_object), 0L, A_GIMME, 0);

if you have the wrong name

eg c = class_new("ar_something_else~"

then I’m guessing it only would instanstaite if you typed that. So you don’t get an object with the "correct" name

And so making sure the class path, xcode and filenames tie up looks important here.


Viewing 4 posts - 1 through 4 (of 4 total)