I am getting a different result in my code when I run a patch as a an abstraction vs on its own. The issue seems to be with a list append object and the right cold inlet. The patch does the following:

1. takes a number input
2. pass the number input to the hot side of the list append
3. if the number input is <= 127, pass 1 to the right cold side of list append else if it is 128 or greater pass 1 + 1 (2) to the right cold side list append.
4. format the list in a message, print the message
5. and also print the value of the data directly.

Here is the abstraction patch:

Here is the main patch:

When I run the main patch and enter 127 then 128 into the number atom I get the following output in the console:

first problem is the number out of range. Second problem is that the $2 value in the message is not the same as the value printed from "print result".

When I run the patch on its own and use the number atom in the patch for the value I get a different output in the console:

In this case the value of "print result" and the $2 value in the message are the same.

It seems there is a difference in the order of execution of the print statements and maybe there is also a difference in order of when the cold inlet on the list append gets updated.

Why is there a difference when run as an abstraction and how do I correct the number out of range error?

thanks for your help.

Here is the abstraction patch download.
k1-test.pd

@hp3 Order of operations.
In the first you must have connected first to the hot inlet. The object only does something when it receives something on the hot inlet.
So the first time there is no $2....... you see the message.
And then your calc goes to the right inlet and nothing happens.
The next time you send a number it is good, but wrong because it is appending the previous number (the first)

In your second picture you must have connected the [127( to the [<= 127] first so it works correctly.
Things will happen in the order in which you connect them, unless you use a trigger.

You should really always use a trigger.... [t f f] in this case, to set the correct order and always send to the hot inlet last to make your stuff happen.
Good bedtime reading......... http://puredata.info/docs/manuals/pd/x2.htm
Chapter 2.3 for your problem.
David.