Philip Curtis

I'm having a problem with the pattr system when using scripts that connect objects inside bpatchers. Even though the objects inside the bpatchers that are being connected via script are not within the visible area of the bpatcher on the top-level patch, where the pattrstorage is, the cables being drawn inside the bpatcher seem to disrupt the graphics of the top-level patch.

It's a little hard to explain, so I've tried to make it clear inside the patch. If my instructions don't make sense, just start clicking and saving and recalling presets, and you'll see the problem.

Here is the bpatcher. Save this with the name "GraphicsProblemBpatcher.pat":

Here is the top-level patch. Open it after saving the above patch with the name give above:

I don't know if this has come up on the list before - I looked but couldn't find anything.

bug-pattr-graphics-problems-with-scripts-inside-bpatchers

In my current patch it's actually the discoloration that I mention (in the comments in the toplevel patch) that is bothering me the the most. I have various ui objects turning various colors (mostly green) for no apparent reason as I recall presets.

I only illustrated the problems with the cables and the scripts inside the bpatchers because it was the easiest one for me to figure out what was going on and how to reproduce it.

Obviously, this isn't really stopping me from working, but it is really kind of annoying to have random lines being drawn inside your patch, and objects turning various colors...

Hi, the "line drawing" problem seems to disappear if you use "scipt hide

You also have the message to max ";max refresh" but it's not super

Hi, the "line drawing" problem seems to disappear if you use "scipt hide
connect ...." inside your Bpatcher.
You also have the message to max ";max refresh" but it's not super
elegant...
Hope that helps.

Thanks! I was unaware of the "hidden connect" script. That works great.

It's a little odd (a bug?) that these graphics issues exist only when recalling with pattr. They don't show up with normal patch use.

It got much worse when I switched from 4.5 on an older mac to 4.6 on an intel machine, incidentally. That's when it started to cause ui objects to change colors.

has anybody here had any success in getting the phidgets InterfaceKit 8/8/8 to work with 

i tried both the phidget20 and phidget21 libraries and MAX/MSP externals. all with clean 

uninstall beforehand. no success whatsoever. the funny thing is that the 

"PhidgetInterfaceKit.help" patch displays a dotted object called "PhidgetInterfaceKit" 

(that usually means, an external is not found or can't be loaded, right ?) but doesn't 

print any error message on the Max console

i also tried the "fidget" external but apart from being recognized by MAX it doesn't seem 

to do anything. maybe it's outdated since last revisal seems to have been in 2003.

please, if anybody here got their phidgets to work with MAX, tell me your secret.

even if it's not exactly the same setup, any experiences are appreciated.

i'm now past several hours of sheer frustration trying to make it work ;-)

has anybody here had any success in getting the phidgets InterfaceKit 8/8/8 to work with 
MAX/MSP Runtime 4.5.7 ?

i tried both the phidget20 and phidget21 libraries and MAX/MSP externals. all with clean 
uninstall beforehand. no success whatsoever. the funny thing is that the 
"PhidgetInterfaceKit.help" patch displays a dotted object called "PhidgetInterfaceKit" 
(that usually means, an external is not found or can't be loaded, right ?) but doesn't 
print any error message on the Max console

i also tried the "fidget" external but apart from being recognized by MAX it doesn't seem 
to do anything. maybe it's outdated since last revisal seems to have been in 2003.

please, if anybody here got their phidgets to work with MAX, tell me your secret.
even if it's not exactly the same setup, any experiences are appreciated.

bug: pattr graphics problems with scripts inside bpatchers