jeremy

i'm creating a java class that loads 10 instances of another class. in this case, i have a particle system that loads a given number of particles. whenever i edit the file for the particles and re-create the mxj object in max (for the particle system), mxj loads the old particle class. how can i ensure that it loads the correct version?

java version "1.5.0_07"
osx 10.4.8
max 4.6


particle-system-class-problems

try sending your mxj instance the 'zap' message before you re- 

On May 1, 2007, at 14:43 PM, jeremy wrote:

> i'm creating a java class that loads 10 instances of another class. 

> in this case, i have a particle system that loads a given number of 

> particles. whenever i edit the file for the particles and re-create 

> the mxj object in max (for the particle system), mxj loads the old 

> particle class. how can i ensure that it loads the correct version?

try sending your mxj instance the 'zap' message before you re- 
instantiate it!
t

>
>
> howdy.
>
> i'm creating a java class that loads 10 instances of another class.  
> in this case, i have a particle system that loads a given number of  
> particles. whenever i edit the file for the particles and re-create  
> the mxj object in max (for the particle system), mxj loads the old  
> particle class. how can i ensure that it loads the correct version?
>
> thanks,
>
> jeremy rotsztain
>
> java version "1.5.0_07"
> osx 10.4.8
> max 4.6


sometimes i find that an older version of the class gets loaded.

fyi, i'm working with eclipse and dragging the .java and .class files into the cycling74 java folder.

sometimes i find that an older version of the class gets loaded.
fyi, i'm working with eclipse and dragging the .java and .class files into the cycling74 java folder.

sorry, i meant to write that the main mxj object (the particle system) also loads an older version every once in a while.

amusingly enough, it turns out that mxj was looking at an older version of the file that was outside of the java class path (in a backup folder on my desktop). i deleted the file and it's now working properly.

Just wanted to mention that you can configure Eclipse to put the built

class files anywhere you want. This might save you the step of

dragging them over all the time. Project properties:Java Build

> amusingly enough, it turns out that mxj was looking at an older version of the file that was outside of the java class path (in a backup folder on my desktop). i deleted the file and it's now working properly.

Just wanted to mention that you can configure Eclipse to put the built
class files anywhere you want.  This might save you the step of
dragging them over all the time.  Project properties:Java Build
Path:Default output folder.

On 5/2/07, jeremy  wrote:
>
>
> amusingly enough, it turns out that mxj was looking at an older version of the file that was outside of the java class path (in a backup folder on my desktop). i deleted the file and it's now working properly.
>
> jeremy
>


particle system class problems