skrasms

If I have something coded in Javascript, and I use two or more instances of it in a Max patch, I'm running into problems with the global variables being "shared" between the javascript instances. That is, if I have global variable called "ohjeeze" in each of the instances, and I want one instance to change ohjeeze to the number 5, it will cause ohjeeze to become 5 in every javascript object I'm using. Is there a way to define variables that are global within a javascript object, but not global within the entire patcher?

It seems like something really simple for which I just don't know the syntax.

making-variables-global-but-not-too-global

On Feb 9, 2007, at 4:42 PM, Aaron Faulstich wrote:

> If I have something coded in Javascript, and I use two or more 

> instances of it in a Max patch, I'm running into problems with the 

> global variables being "shared" between the javascript instances. 

> That is, if I have global variable called "ohjeeze" in each of the 

> instances, and I want one instance to change ohjeeze to the number 

> 5, it will cause ohjeeze to become 5 in every javascript object I'm 

> using. Is there a way to define variables that are global within a 

> javascript object, but not global within the entire patcher?

> It seems like something really simple for which I just don't know 

Sounds like you need to use the var keyword before your variable 

>
> If I have something coded in Javascript, and I use two or more  
> instances of it in a Max patch, I'm running into problems with the  
> global variables being "shared" between the javascript instances.  
> That is, if I have global variable called "ohjeeze" in each of the  
> instances, and I want one instance to change ohjeeze to the number  
> 5, it will cause ohjeeze to become 5 in every javascript object I'm  
> using. Is there a way to define variables that are global within a  
> javascript object, but not global within the entire patcher?
>
> It seems like something really simple for which I just don't know  
> the syntax.

Sounds like you need to use the var keyword before your variable  
declaration. *important*.

After going through and making sure everything in the global declarations had a "var" in front of it, the patcher now crashes whenever I have two instances of that javascript object. I never previously had any crashes.

Actually I should be more specific. Technically I'm running two instances of the javascript object across two instances of a Pluggo VST. Does that play by different rules than a regular patch?

On Feb 10, 2007, at 7:40 AM, Aaron Faulstich wrote:

> Actually I should be more specific. Technically I'm running two 

> instances of the javascript object across two instances of a Pluggo 

> VST. Does that play by different rules than a regular patch?

No, but since you haven't given us much information, all we can do is 

speculate. Whenever trying to isolate a problem, you'll want to try 

and narrow down your issues as much as possible and identify the 

criteria that causes the problem to be exposed. If you can clearly 

communicate your problem in this way, then people can offer more 

There should be no problems introduced based strictly on the 

introduction of the var keyword, however, perhaps you can post some 

code, your platform, OS version, Max/MSP version, Pluggo host, etc. 

etc. so we actually have something to talk about.

>
> Actually I should be more specific. Technically I'm running two  
> instances of the javascript object across two instances of a Pluggo  
> VST. Does that play by different rules than a regular patch?

No, but since you haven't given us much information, all we can do is  
speculate. Whenever trying to isolate a problem, you'll want to try  
and narrow down your issues as much as possible and identify the  
criteria that causes the problem to be exposed. If you can clearly  
communicate your problem in this way, then people can offer more  
assistance.

There should be no problems introduced based strictly on the  
introduction of the var keyword, however, perhaps you can post some  
code, your platform, OS version, Max/MSP version, Pluggo host, etc.  
etc. so we actually have something to talk about.

Okay, sorry for being so vague. I'm running Max/MSP 4.6.2. I' using the newest Pluggo runtime in Cubase SX3 under Windows XP Service Pack 2.

I've attached the code in question. It's a JSUI object for quick file navigation of a few file extensions. Before adding "var" in front of all the variables, if I ran two plugin instances it would just cause some conflicts with data meant to transfer inside one instance ending up in both instances. Now that I've added "var," if two instances are open then Cubase SX crashes when the mouse goes over either JSUI instance. It appears to involve the ondrag function, as I don't have to click anything to cause a crash, just mouse over the JSUI.

I hope that helps. Please let me know if you need any more information, and thank you for showing interest.

Okay, sorry for being so vague. I'm running Max/MSP 4.6.2. I' using the newest Pluggo runtime in Cubase SX3 under Windows XP Service Pack 2. 

I've attached the code in question. It's a JSUI object for quick file navigation of a few file extensions. Before adding "var" in front of all the variables, if I ran two plugin instances it would just cause some conflicts with data meant to transfer inside one instance ending up in both instances. Now that I've added "var," if two instances are open then Cubase SX crashes when the mouse goes over either JSUI instance. It appears to involve the ondrag function, as I don't have to click anything to cause a crash, just mouse over the JSUI. 

I hope that helps. Please let me know if you need any more information, and thank you for showing interest.


After more testing I've found out some more details:

Putting two instances of the JSUI object into one patcher doesn't cause any conflicts that I can see. It is only when two different instances of a plugin use it that there is a problem.

The crashing doesn't always occur under the same condition. A couple times I was able to mouse over the second JSUI instance in Cubase without a crash. For those times it didn't crash until I tried loading a folder.

Putting two instances of the JSUI object into one patcher doesn't cause any conflicts that I can see. It is only when two different instances of a plugin use it that there is a problem. 

The crashing doesn't always occur under the same condition. A couple times I was able to mouse over the second JSUI instance in Cubase without a crash. For those times it didn't crash until I tried loading a folder. 

Making variables global, but not TOO global