function. however, even if you are not passing arguments to the
function, you need to use an empty pair of parentheses. this tells
the script that you are trying to call a function and not reference a
property. in other words, change your code to this:
On Dec 20, 2005, at 1:56 PM, firstname.lastname@example.org wrote:
> Actually I tried making firstobject and nextobj methods but MAX
> tells me that they are not functions. Any other ideas why this
> does not work?
They are both *properties*, but please notice your typo. It is not
"nextobj", but "nextobject" as documented in the latest
10.4.3, and MaxMSP 4.5.6.
have you tried joshua's suggestion which you quoted?
perhaps the nextobject property for the last object isn't null. just
try "while(obj)". this would explain max locking up, because you would
be stuck in an endless loop.
On around Jan 25, 2006, at 2:06, jim altieri said something like:
> try "while(obj)".
while (obj != NULL)
are identical statements. The only difference is programming style (ie,
identical code for both conditionals, you've got a buggy
That said, Anthony's code looks fine and I don't immediately see why it
should lock up. Stupid question: are you very sure the syntax to the
outlet() call is OK?
Well, I'd expect my Java compiler to reject both of them: the first
unless obj is a boolean (or, under Java 1.5, a Boolean object with
auto-unboxing) and the second unless NULL is defined and is
compatible with the type of obj, since Java uses the lower-case form.
nick rothwell -- composition, systems, performance -- http://