asdrubale

Given this js object, sending message "test" to inlets works, but sending "myobj.test" doesn't work. Why?

	this.test = function (){
		post('OK');
	};

error-sending-message-to-js

Hi. What exactly do you mean by 'sending myobj.test'?

Well, you simply cannot address variables/objects directly with a Max message. The Max JavaSript API allows you to call functions inside your [js] by sending the function name as a message. That's why the message "test" works and "myobj.test" not. You are calling the function test and this function is calling the method of your object.

I assume that you are aiming for a better encapsulated code by instantiating a JS "class" (yes there are no real classes in JS i know :) ). But you will still need to write a function to call the method inside your object. But IMHO it doesn't really make sense within a [js] except you need several instances of your "class" i.e. with different property values:

In this scenario you can send the message "test myobj1" or "test myobj2" and you can adddress different instances.

But what exactly do you want to achieve with this? it is not clear to me.

Well, you simply cannot address variables/objects directly with a Max message. The Max JavaSript API allows you to call functions inside your [js] by sending the function name as a message. That's why the message "test" works and "myobj.test" not. You are calling the function test and this function is calling the method of your object.
I assume that you are aiming for a better encapsulated code by instantiating a JS "class" (yes there are no real classes in JS i know :) ). But you will still need to write a function to call the method inside your object. But IMHO it doesn't really make sense within a [js] except you need several instances of your "class" i.e. with different property values:

In this scenario you can send the message "test myobj1" or "test myobj2" and you can adddress different instances.
But what exactly do you want to achieve with this? it is not clear to me.

hi Lee, sending "myobj.test" as a message to the js inlet.

If you look at the script I've a function named "test". I can execute this function by sending a message, and that's ok (and documented).

My problem is how I can call the function "test" of object "myobj".

hi Lee, sending "myobj.test" as a message to the js inlet.
If you look at the script I've a function named "test". I can execute this function by sending a message, and that's ok (and documented).
My problem is how I can call the function "test" of object "myobj".

oupps cross posting, i think i just answered it :)

if you also also want to expose the method directly you can do the following:

The Max messages then would be "test myobj1 testMethod" or "test myobj2 testMethod".

The Max messages then would be "test myobj1 testMethod" or "test myobj2 testMethod".


I'm not a "patch" guy, I'm a max noob and a seasoned software developer. It's easier to me to use javascript for everything , that's all.

But I suspect is not the way Max works :-)

I'm not a "patch" guy, I'm a max noob and a seasoned software developer. It's easier to me to use javascript for everything , that's all.
But I suspect is not the way Max works :-)


Yea, the two approaches are quite different. I do both quite a lot, patching and coding, so i do understand :)

The way JavaScript is implemented in Max might lead to very old school procedural code. That's just how it is. But after thinking for a moment there is something that i like about your approach: This way one can work with a single entry point.

In Max there is also the reserved function "anything" which is called when no matching function is found. So one could tighten it up a bit with:

function anything(methodName) {
    this[messagename][methodName]();
}


and simply send "myobj1 testMethod" to js.

function anything(methodName) {
	this[messagename][methodName]();
}


and simply send "myobj1 testMethod" to js.


Error sending message to js