maxmsp@codeoperator.c

it seems that there is a bug in the Pluggo 3.6 "pp" object. The "pp" 

object should output any change to the stored value, but it doesn't. 

This patch works perfect with Max 3.5.x and Pluggo 3.5.x...

Is this really a bug or am I doing something wrong?

it seems that there is a bug in the Pluggo 3.6 "pp" object. The "pp" 
object should output any change to the stored value, but it doesn't. 
This patch works perfect with Max 3.5.x and Pluggo 3.5.x...

bug-in-pp-object

My main problem is that "pp" only output the stored value by receiving a bang in the input!

My main problem is that "pp" only output the stored value by receiving a bang in the input!
Can anyone confirm this?


It's not a bug but a feature introduced in max 4.6

On Oct 13, 2006, at 1:40 AM, Jan Thiele wrote:

> it seems that there is a bug in the Pluggo 3.6 "pp" object. The 

> "pp" object should output any change to the stored value, but it 

> doesn't. This patch works perfect with Max 3.5.x and Pluggo 3.5.x...

> Is this really a bug or am I doing something wrong?

I was having the same difficulty until Tim Place got me sorted. [pp] 

needed to be changed for host compatibility in some apps.

> it seems that there is a bug in the Pluggo 3.6 "pp" object. The  
> "pp" object should output any change to the stored value, but it  
> doesn't. This patch works perfect with Max 3.5.x and Pluggo 3.5.x...
>
> Is this really a bug or am I doing something wrong?

I was having the same difficulty until Tim Place got me sorted.  [pp]  
needed to be changed for host compatibility in some apps.

Vlad Spears
Urbi et orbi
http://www.2secondfuse.com

Bug in pp object?