[java-dev] Re: MXJ getting wrong inlet

Just for kicks I made a patch and mxj to replicate the problem. On my system this demonstrates both the mxj getInlet() problem, and the trace crashing max problem. The interesting thing for me, though, is that it doesn't explain why one instance of my full network patch actually worked correctly... very strange, indeed.

The patch deliberately makes a loop, so run it with trace enabled! Then you can end your test session with max crashing on the trace problem! ;-)

It would be interesting to see whether this problem is 10.5 (or 10.5.2) specific.

J.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: outletMania.zip
Type: application/zip
Size: 2130 bytes
Desc: not available
Url : http://www.cycling74.com/pipermail/java-dev/attachments/20080329/48ba26f3/outletMania.zip