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
Intel and PPC affected.
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.
would the message
be of any help?
possibly, but because that can stall the scheduler in redrawing a
sufficiently complex patch, max should be doing it regardless.
v a d e //
On Nov 5, 2006, at 6:35 AM, nesa wrote:
> would the message
> ;max refresh
> be of any help?
Log in to reply
Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.