The easiest way is to create a print object using object_new() and then send messages to it using object_method().

Cheers, Tim

But if I'm not wrong this wouldn't allow me to double-click a line in the max window and have my object highlighted. ... or am I wrong? aa

@andrea: true.

I guess I'm not sure what exactly you are trying to do or why you are trying to do this. However, the ecology of the Max environment is such that people expect the object name to be in the left column and any other info to be in the right column. So it's generally advised to follow the convention that everyone expects and the API doesn't make a lot of accommodation for doing otherwise.

best wishes, Tim

Tim, I see your point.

What I'm trying to do is implementing a custom data type (thank you for your articles on 74objects, btw!), and having a "post" object that mimics as closely as possible the behaviour of print - so, in fact, I think I am totally respecting the Max ecology! ;)

imho, the API should ideally allow for virtually every behaviour implemented in the native Max objects. While this may not be fully applicable in very extreme cases (I understand grab is one of those), I think that in general it should be left up to the developer's choice if and how much to deviate from an average "standard" behaviour for a specific purpose. In fact, it's true that this is basically what already happens, but I'd love to have even more...

Thank you anyway! aa