djlbe

reinstanciate-a-java-class-with-mxj-zap-message-problem

Calling methods inside a constructor is not advisable, because the instantiation is not yet finished, for initializing variables it's ok. What I always do is to make an "init" method that is called manually to do more complex initialization routines.

If you delete the methods inside your constructor, will then the delete/undo trick work for you? It works over here, I'm on Windows 7 64-bit and Max 7.

I don't get it. In fact, even if I close the patcher containing the mxj, the mxj seems to stay in memory. the bang method isn't a loadbang so I'm a bit lost :/ what my code should looks like ? Where should i place that's bang method then ? does it ever worked for you under Max 6 ? I'm not using Max 7 for the moment

Hmm, I've took your example code and it just works over here, change some code, save it in Eclipse, do delete/undo and the change in code is carried out. We have an almost similar setup, but with a few changes. My specs are Windows 7 64-bit, Max 6.1.5 and I use Eclipse too although I use JVM 1.7 Maybe the change in JVM could be worth investigating?

I use a 32bit version of Max 6.1.9. I tried to use JVM 1.7 by changing the project settings in Eclipse and the JVM compliance level to 1.7 too.

In desperation, I tried to modify a bit the max.java.config.txt by uncommenting some stuffs like :

I begin to think that you are right with my code, have you an idea of something I could try ? my knowledge of the Java langage lacks a bit so it's hard for me to think about a workaround

I use a 32bit version of Max 6.1.9. I tried to use JVM 1.7 by changing the project settings in Eclipse and the JVM compliance level to 1.7 too.
In desperation, I tried to modify a bit  the max.java.config.txt by uncommenting some stuffs like :
  max.jvm.option -Xdebug
  max.jvm.option -Xnoagent

I begin to think that you are right with my code, have you an idea of something I could try ? my knowledge of the Java langage lacks a bit so it's hard for me to think about a workaround


Hi, from what I can recall, this got broken in 6.1.9 - it was raised during the 7 beta and the response as that there wasn't any intention of addressing this in 6 - so, I'd suggest moving back to 6.1.8 if you can, or move forward to 7... You can always ask for this to be fixed, but as said, unlikely to happen for 6....

I tried also to change of version, I tried : 6.0.5 32bit and 6.1.9 64bit, and I read that the prob appears at least on 6-1-7 (look at the link of my first message)

Maybe it was 6.1.7 then - it was a long time ago I remember that... btw, note this is a Max bug, it has nothing to do with the jvm that is being used...

Just looked back through my mail history and I raised it for 6.1.9 - maybe it had existed before and I hadn't noticed as I wasn't doing any Java dev at that point...

Arf, but that's strange then if it doesn't works on the 6.0.5 no ? I was pretty sure about the JVM it looks like the mxj get stuck in the memory for ever.

and about the 6.1.10 version, do you know if it has been corrected ?

it means that there will be a fantastic 6.2 version then :D ? (you know , they updated Windows XP until the 8th april 2014 so...)

and about the 6.1.10 version, do you know if it has been corrected  ? 

it means that there will be a fantastic 6.2 version then :D ? (you know , they updated Windows XP until the 8th april 2014 so...)


As far as I know, there are no more planned 6 releases and it was stated in my last conversation with then about this issue in Oct 14 that they were not going to put resource into fixing this in 6... It does work fine in 7...

maybe the time has comes to make an upgrade : / glad I'm a student again and that I have already Max 6

Max 7 is well worth the upgrade - after using it for a short while you won't miss 6 at all :)

However, if you make a standalone of your max patch that other people use beware that Max 7 creates huge file sizes (like 300 Mb!). Not so with Max 6 and that's THE reason I switched back to 6.

This has been worked on - i know it has been reducing - have you tried with the latest 7.0.5?

Also, as far as having the benefits of still being able to use 'zap', you can still do all the work in 7 and build in 6....

Now that's weird :/ I'm on Max 7.0.5 64bit, zap message doesn't do anything, and the fact to close and open the patch again doesn't work too. same situation than before

Ok ! I finally found the reason of my problem, In my max.java.config.txt I was using :

max.SYSTEM.class.dir C:/Projet~3/max_t/bin instead of

what a stupid mistake -_- I will whip myself all the night, sorry for the mess

Ok ! I finally found the reason of my problem, In my max.java.config.txt I was using :
max.SYSTEM.class.dir C:/Projet~3/max_t/bin instead of
max.DYNAMIC.class.dir 

what a stupid mistake -_- I will whip myself all the night, sorry for the mess
