I'm having an issue with mxj and the corresponding object's code path. I'm running Max 5.05 on Win XP. The classpath is the default.
I keep all my java class code (source and compiled) in C:/Program Files/Cycling '74/Max 5.0/Cycling '74/java/classes. However, I keep my Max patcher files on my D: drive.
If I have a patch with a java object, once the patch is saved on the D: drive, I can't open the source code. The Max window says it's looking for D:/program files... (etc) for some reason instead of C:/program files... (etc).
The weird thing is that the patch still runs fine. I can save and open it, and it loads the object without a problem. But Max keeps looking to the D: drive for the class source file, so I can't edit it. This makes developing very difficult.
If I save the Max patcher file on the C: drive then I am able to open and edit the java object as expected.
I guess the Max patcher file has to be on the same drive as the java class? I've tried a whole bunch of things to get around it but nothing works. Anybody have any suggestions?
thanks - steve
PS - also, double-clicking on the mxj object no longer opens the java source code, even when both files are on the C drive. It literally stopped working one day. I always have to use a "viewsource" message. I've even re-installed MAX but it didn't fix it.