vade

The following patch works in the full editing environment.

press the various messages to script connect/disconnect the buttons. 

The patch cords in the editing environment properly disconnect.

It behaves properly in the runtime, however there are graphical 

glitches, the patch cords do not get removed. the logic remains 

Not drawing 'script disconnect a 0 b 0' style messages/deleted patch 

cords. The connection does not exist however.

Patch cords disconnect and are visually removed.

This is a major pain for debugging patches runtime - and freaked us 

all out untill we realized the connection didnt in fact exist.

considering max is a graphical programming language, it would be nice 

for the graphics to reflect the logical state - even in the runtime.

press the various messages to script connect/disconnect the buttons.  
The patch cords in the editing environment properly disconnect.

It behaves properly in the runtime, however there are graphical  
glitches, the patch cords do not get removed. the logic remains  
functional.

Not drawing 'script disconnect a 0 b 0' style messages/deleted patch  
cords. The connection does not exist however.

This is a major pain for debugging patches runtime - and freaked us  
all out untill we realized the connection didnt in fact exist.

considering max is a graphical programming language, it would be nice  
for the graphics to reflect the logical state - even in the runtime.

runtime-bug

possibly, but because that can stall the scheduler in redrawing a 

sufficiently complex patch, max should be doing it regardless.

possibly, but because that can stall the scheduler in redrawing a  
sufficiently complex patch, max should be doing it regardless.

> would the message
>
> ;max refresh
>
> be of any help?
>
> best,
> nesa
