Myla

The 'if' is missing from my externals library, I have searched Max Objects which indicates it should be available to me as an external and is not in my Max 5 external folder. I have done a search in my other Max folders and it is not there either. Can anobody advise where I can download this object?

looking-for-if-object

That's weird : I got no problem using [if] (the if maxhelp works nice, etc.), but I can't find the if external either (on a windows 5.0.7 version).I just noticed that I can't find expr.mxe as well.

And those ones are not present in max-objectmappings.txt...

That's weird : I got no problem using [if] (the if maxhelp works nice, etc.), but I can't find the if external either (on a windows 5.0.7 version).I just noticed that I can't find expr.mxe as well.
And those ones are not present in max-objectmappings.txt...
Sure we miss something here...
How does that work?

No need to 'download' it. [if] is an internal object, it's built into the Max application.

Thanks for the pointer - i found it in the help folder however Max only recognises it as an objec if I actaully type the beginning of the statement eg if $i1 then and then it recognises the object. If I just type if on its own it cannot find the object. My file preferences path is correct.

Thanks for the pointer - i found it in the help folder however Max only recognises it as an objec if I actaully type the beginning of the statement eg if $i1 then  and then it recognises the object.  If I just type if on its own it cannot find the object.  My file preferences path is correct.

Thats how it is supposed to be, it requires the correct arguments to work or it won't instantiate properly, which makes sense as it wouldn't do anything if the arguments were invalid anyway. However it could be a bit confusing if you're new to max. You can still alt+click on it to get the help file, if you need clues.

[zl] with wrong or no arguments is also [zl], so 

but most people also dont know that you can 

write [1 2 3] in order to get a [list] object.

dont seek the logic behind max, build it in max.

[zl] with wrong or no arguments is also [zl], so 
why not [if]?

but most people also dont know that you can 
write [1 2 3] in order to get a [list] object.

If I just type if on its own it cannot find the object.

It works for me, if I only type "if", the error message is:

It is instantiating, and I can even open the help with alt-click...

If it wouldn't find it the error would be "no such object"

Myla wrote on Fri, 08 May 2009 15:33If I just type if on its own it cannot find the object.

It works for me, if I only type "if", the error message is:
if: missing then
It is instantiating, and I can even open the help with alt-click...

Thank you for all the replies .. yes I am quite new to max so I am continuously discovering.. and as you say interestingly enough with the [zl] object Max locates it without having to type any further arguments. To avoid any confusion the message in max window when I just type [if] is no such object.

Thank you for all the replies .. yes I am quite new to max so I am continuously discovering.. and as you say interestingly enough with the [zl] object Max locates it without having to type any further arguments.  To avoid any confusion the message in max window when I just type [if] is no such object.

i found it in the help folder however Max only recognises it as an objec if I actaully type the beginning of the statement eg if $i1 then and then it recognises the object. If I just type if on its own it cannot find the object. My file preferences path is correct.

What you found in the help folder is if.help/if.maxhelp. That's the help file, not the .mxo.

As I wrote previously, there is no .mxo. [if] is built into the Max kernel.

The fact that if behaves differently from zl when no arguments are given is because [if] and [zl] are two different objects. Each object does its own error handling. Any similarity in the error handling of two different objects is, by and large, coincidental. In particular, zl always has two inlets whereas if has to parse its argument list to determine how many inlets to sprout. There is a compelling reason for the two objects to behave differently in this regard.

Myla wrote on Fri, 08 May 2009 15:33i found it in the help folder however Max only recognises it as an objec if I actaully type the beginning of the statement eg if $i1 then  and then it recognises the object.  If I just type if on its own it cannot find the object.  My file preferences path is correct.

The fact that if behaves differently from zl when no arguments are given is because [if] and [zl] are two different objects. Each object does its own error handling. Any similarity in the error handling of two different objects is, by and large, coincidental. In particular, zl always has two inlets whereas if has to parse its argument list to determine how many inlets to sprout. There is a compelling reason for the two objects to behave differently in this regard.


Looking for 'if' object