vodstrup

It's been a few months since I've been under the hood of this patch -

please forgive me if my terminology is a bit rusty.

http://www.timbitson.com/Weather_Projects.html)

sending data into max through java/mxj. If I can get the class/object

to load properly, it works great. Here's the problem:

2. Boot up the computer (Mac PPC 10.4.11)

3. Open the "weather" patch in max (4.6.3)

4. The patch opens but shows these errors:

error: connect: outlet 2 of mxj out of range

error: connect: outlet 3 of mxj out of range

error: connect: outlet 4 of mxj out of range

error: connect: outlet 5 of mxj out of range

error: connect: outlet 6 of mxj out of range...

Also, I need to send "start" and "stop" messages to the mxj object in

order to start/stop the polling of the sensors.

when I click the message box I get this error:

error: simpleWeather.SimpleWeather doesn't understand start

5. Here's the trick... I close max and delete

simpleWeather.SimpleWeather.jar in the classes folder.

6. I rebuild the .jar in netbeans and then place it in the classes folder.

7. I open Max and make a new MXJ object and (beach ball for 2 seconds)

then the object loads perfectly. I close this patch w/o saving.

8. Open the "weather" patch in Max and now it works.

9. I'm happy that I can get it to work, but this piece needs to be

installed in a gallery in a few months and I can't expect the gallery

It's probably a simple oversight on my part as I am only an

accomplished Java hacker and not a programmer. It seems to me that it

is a problem relating to how I am declaring my outlets, or how the

"extends MaxObject implements Runnable" get initiated. However, that

wouldn't explain why it works fine after a rebuild and replaced in the

I'm not sure what to send along, but have attached the .jar and will

paste the max patch below. As always I deeply appreciate any/all help

with this - hopefully it's something simple and obvious (usually is).

Note: if I try to open a new patch and make a new mxj object (w/o

rebuilding the .jar) and type in the class simpleWeather.SimpleWeather

It's been a few months since I've been under the hood of this patch -
please forgive me if my terminology is a bit rusty.

I have one of Tim Bitson's
(http://www.timbitson.com/Weather_Projects.html) weather stations
sending data into max through java/mxj.  If I can get the class/object
to load properly, it works great.  Here's the problem:

1. Plug in the USB weather station
2. Boot up the computer (Mac PPC 10.4.11)
3. Open the "weather" patch in max (4.6.3)
4. The patch opens but shows these errors:

error: connect: outlet 2 of mxj out of range
error: connect: outlet 3 of mxj out of range
error: connect: outlet 4 of mxj out of range
error: connect: outlet 5 of mxj out of range
error: connect: outlet 6 of mxj out of range...

Also, I need to send "start" and "stop" messages to the mxj object in
order to start/stop the polling of the sensors.

5.  Here's the trick... I close max and delete
simpleWeather.SimpleWeather.jar in the classes folder.

7. I open Max and make a new MXJ object and (beach ball for 2 seconds)
then the object loads perfectly.  I close this patch w/o saving.

9. I'm happy that I can get it to work, but this piece needs to be
installed in a gallery in a few months and I can't expect the gallery
staff to hack my max patch...

It's probably a simple oversight on my part as I am only an
accomplished Java hacker and not a programmer.  It seems to me that it
is a problem relating to how I am declaring my outlets, or how the
"extends MaxObject implements Runnable" get initiated.  However, that
wouldn't explain why it works fine after a rebuild and replaced in the
classes folder.

I'm not sure what to send along, but have attached the .jar and will
paste the max patch below.  As always I deeply appreciate any/all help
with this - hopefully it's something simple and obvious (usually is).

Note: if I try to open a new patch and make a new mxj object (w/o
rebuilding the .jar) and type in the class simpleWeather.SimpleWeather
- it crashes Max.

error-connect-outlet-2-of-mxj-out-of-range

Update: I was able to get this to work. When the mxj would load w/o the outlets, I put a viewsource message into it and noticed that it was seeing the very first script I authored with that name.

This is strange because this class didn't exist in the classpath - hadn't for a long time. In fact, I have no idea where this class was located.

I deleted everything relating to this: the patch, the classes, the Java code... I then started from scratch (rebuilt the Java, imported the .jar into the classpath, etc.) and now it appears to be working quite well.

Anyone know where that old script was lingering? Since it wasn't in my classpath, how could the mxj see it? and why, after putting in a new class, did max still want to load the old one?

Is there a possibility that my classpath is pointing to somewhere in addition to the classes folder?

Update: I was able to get this to work.  When the mxj would load w/o the outlets, I put a viewsource message into it and noticed that it was seeing the very first script I authored with that name.

This is strange because this class didn't exist in the classpath - hadn't for a long time.  In fact, I have no idea where this class was located.  

I deleted everything relating to this: the patch, the classes, the Java code...  I then started from scratch (rebuilt the Java, imported the .jar into the classpath, etc.) and now it appears to be working quite well.

Anyone know where that old script was lingering?  Since it wasn't in my classpath, how could the mxj see it?  and why, after putting in a new class, did max still want to load the old one?