Adam Murray

1. The ability to disable toggling sustain points (command/control clicking). In other words, support a "clicksustain 0/1" message. Right now this seems to be coupled to the option to disable dragging breakpoints. I have a UI where I want the user to be able to drag the breakpoints around, but not delete or add points or change the sustain point.

2. Output information about the current sustain points. I discovered I can access this information using the pattr system, but the format is not ideal because I have to parse the pattr value. I'd prefer to send a message that causes function to output a list of the point indices that have sustain enabled, or perhaps a list of 0's and 1's for each point (1=sustain, 0=not).

As usual with Max, there is a workaround. See my patch below. But I believe implementing the above features directly in the function object would make the Max user's life easier.

1. The ability to disable toggling sustain points (command/control clicking). In other words, support a "clicksustain 0/1" message. Right now this seems to be coupled to the option to disable dragging breakpoints. I have a UI where I want the user to be able to drag the breakpoints around, but not delete or add points or change the sustain point. 

As usual with Max, there is a workaround. See my patch below. But I believe implementing the above features directly in the function object would make the Max user's life easier. 

feature-requests-for-function-object

On 31 juil. 07, at 09:22, Adam Murray wrote:

> 1. The ability to disable toggling sustain points (command/control 

> clicking). In other words, support a "clicksustain 0/1" message. 

> Right now this seems to be coupled to the option to disable 

> dragging breakpoints. I have a UI where I want the user to be able 

> to drag the breakpoints around, but not delete or add points or 

> 2. Output information about the current sustain points. I 

> discovered I can access this information using the pattr system, 

> but the format is not ideal because I have to parse the pattr 

> value. I'd prefer to send a message that causes function to output 

> a list of the point indices that have sustain enabled, or perhaps a 

> list of 0's and 1's for each point (1=sustain, 0=not).

In the meantime, you may have a look to ej.function which implement 

> As usual with Max, there is a workaround. See my patch below. But I 

> believe implementing the above features directly in the function 

> object would make the Max user's life easier.

> 1. The ability to disable toggling sustain points (command/control  
> clicking). In other words, support a "clicksustain 0/1" message.  
> Right now this seems to be coupled to the option to disable  
> dragging breakpoints. I have a UI where I want the user to be able  
> to drag the breakpoints around, but not delete or add points or  
> change the sustain point.

> 2. Output information about the current sustain points. I  
> discovered I can access this information using the pattr system,  
> but the format is not ideal because I have to parse the pattr  
> value. I'd prefer to send a message that causes function to output  
> a list of the point indices that have sustain enabled, or perhaps a  
> list of 0's and 1's for each point (1=sustain, 0=not).

In the meantime, you may have a look to ej.function which implement  
something equivalent.

> As usual with Max, there is a workaround. See my patch below. But I  
> believe implementing the above features directly in the function  
> object would make the Max user's life easier.

Quote: Emmanuel Jourdan wrote on Tue, 31 July 2007 07:29

----------------------------------------------------

> In the meantime, you may have a look to ej.function which implement 

I definitely like the features you put in ej.function and hope many of them get implemented in the standard function object.

I have a minor problem. Every time I move the mouse over the ej.function object, I see this error in the Max window:

error: js: ej.function.js: Javascript ReferenceError: setcursor is not defined, line 530

error: js: error calling function onidleout

This is ejies 1.57 & Max 4.6.3 running on Intel Mac OS X 10.4.10. I used your install.command and selected 'Y' for everything. It appears setcursor() is not defined so I commented it out, then the error went away and the object appears to work properly.

Also I have a usability suggestion. It is useful that you have a shortcut to switch between functions (command + double click), but if I want to toggle a sustain point I have to command+click. If I try to toggle the same point back and forth it often registers as a double click and switches functions when I am trying to toggle sustain, unless I click very slowly. It would probably be better to make the key for switching functions different to avoid interference like this.

BTW this is a very nice set of objects. 3D ej.linterp is great!

Quote: Emmanuel Jourdan wrote on Tue, 31 July 2007 07:29
----------------------------------------------------
> In the meantime, you may have a look to ej.function which implement  
> something equivalent.
----------------------------------------------------

I definitely like the features you put in ej.function and hope many of them get implemented in the standard function object. 

error: js: ej.function.js: Javascript ReferenceError: setcursor is not defined, line 530
error: js: error calling function onidleout

On 31 juil. 07, at 19:02, Adam Murray wrote:

> I definitely like the features you put in ej.function and hope many 

> of them get implemented in the standard function object.

> I have a minor problem. Every time I move the mouse over the 

> ej.function object, I see this error in the Max window:

> error: js: ej.function.js: Javascript ReferenceError: setcursor is 

> error: js: error calling function onidleout

> This is ejies 1.57 & Max 4.6.3 running on Intel Mac OS X 10.4.10. I 

> used your install.command and selected 'Y' for everything. It 

> appears setcursor() is not defined so I commented it out, then the 

> error went away and the object appears to work properly.

Yep, this is a problem with maxtoolbox installed. You need to move 

the toolbox-start file (or whatever it's called) in the init folder 

to max-startup folder, and the error messages should disappear. 

setcursor is part of the Max JS predefined functions.

> Also I have a usability suggestion. It is useful that you have a 

> shortcut to switch between functions (command + double click), but 

> if I want to toggle a sustain point I have to command+click. If I 

> try to toggle the same point back and forth it often registers as a 

> double click and switches functions when I am trying to toggle 

> sustain, unless I click very slowly. It would probably be better to 

> make the key for switching functions different to avoid 

It was a tough choice because shift is also used, and option is 

> BTW this is a very nice set of objects. 3D ej.linterp is great!

> I definitely like the features you put in ej.function and hope many  
> of them get implemented in the standard function object.
>
> I have a minor problem. Every time I move the mouse over the  
> ej.function object, I see this error in the Max window:
>
> error: js: ej.function.js: Javascript ReferenceError: setcursor is  
> not defined, line 530
> error: js: error calling function onidleout
>
> This is ejies 1.57 & Max 4.6.3 running on Intel Mac OS X 10.4.10. I  
> used your install.command and selected 'Y' for everything. It  
> appears setcursor() is not defined so I commented it out, then the  
> error went away and the object appears to work properly.

Yep, this is a problem with maxtoolbox installed. You need to move  
the toolbox-start file (or whatever it's called) in the init folder  
to max-startup folder, and the error messages should disappear.  
setcursor is part of the Max JS predefined functions.

> Also I have a usability suggestion. It is useful that you have a  
> shortcut to switch between functions (command + double click), but  
> if I want to toggle a sustain point I have to command+click. If I  
> try to toggle the same point back and forth it often registers as a  
> double click and switches functions when I am trying to toggle  
> sustain, unless I click very slowly. It would probably be better to  
> make the key for switching functions different to avoid  
> interference like this.

It was a tough choice because shift is also used, and option is  
generally used for open the help file.

feature requests for function object