max5-parsing-max4-patches-bpatcher-scripting-name-bug

Regarding the bpatcher issue, i can reproduce, but only when the bpatcher patcher file exists in both Max 4 and Max 5 search paths.

Also, I can reproduce the filtergraph~ and number~ issues. I will pass these along.

I cannot reproduce the fpic issue when there is an image actually selected. Here, Max 5 respects the offset that was selected in Max 4.

Also, I can reproduce the filtergraph~ and number~ issues.  I will pass these along.

I cannot reproduce the fpic issue when there is an image actually selected.  Here, Max 5 respects the offset that was selected in Max 4.

Since this topic is not about externals development, I'm moving it to the Max/MSP forum.

max5 parsing max4 patches - bpatcher scripting name bug