Polina Vasanti

I have a pretty simple problem that I'm sure has been solved many times.

I have two number boxes that feed into each other, adjusting according to the output of the other.  I'd like to be able to input a value into either of them and have them trigger and output. 

Right now, I am using a "set" message, which strips the "bang" - this is a problem since I would like the output to read elsewhere in a patch. 

Is the only solution to add a manual bang to this? 

I have a pretty simple problem that I'm sure has been solved many times.
I have two number boxes that feed into each other, adjusting...

number-into-number-feedback

Adding a manual bang would still cause a stack overflow. But what you can do is to duplicate the output of one of the two number boxes using a [trigger f f] (or shortened as [t f f ]). One would go to the set message to update the number box, and the other to wherever you want that number to be sent.

Also, rather than updating the patcher file, just select the relevant objects, then go to Edit -> Copy compressed, and paste the result here. It prevents people from having to download a file, then delete it.

Ok - I think I understand that you can have them both display at the same time, but there is no way to have both number boxes update simultaneously? 

to "sync" two GUI elements they simply have to 

things like plug-in parameter, preset system, midi control, will then just be connected to one of them (usually the one of higher resolution/float) and all will be good.

the message order does not matter at all, but it can still be wise to start out with a trigger object as it might be required later in the patching process.

When you say "have both number boxes update simultaneously" I assume you want to say something like "have both number box output their value simultaneously".

First, friendly reminder that in the context of a computer, and especially in the context of a Max patch, things happen sequentially, one after the other. Very quickly, wich makes us feel it happens "at the same time", but still one after the other.

In Max, when you connect the same outlet of an object to two other objects, one of these two objects will always receive data from that outlet 

 the other object. That object is usually the one which is the most in the bottom right of the patcher window, because this is how Max work. 

As Roman say, the order of execution is not important in your case (for now at least), but I just wanted to explain all this to show that things never happen simultaneously here.

Now the question is why would you have both your number boxes to output a value when you can get these values from somewhere else just like in the example in my previous post? You could make both number boxes to output something everytime one or the other is updated, but that would require some boring and overcomplicated gate system to prevent a stack overflow (infinite loop)

The var abstraction and pvar object might be helpful here 

Number into Number Feedback