I don't think this is a boundary issue, it appears to be a bug (though why it took so long to manifest, I don't know). As the two of you have found, the "=%var2%" seems to be the cause of the issue (it should work as written, but obviously that's not the case).
Though I'm not sure what you mean when you say you need to pass the result to the group to "store state"; variables in a table are global, so you don't need to pass anything to a group, you can just store what you need in a variable.
©\©\©\©\©\©\©\ Original Message ©\©\©\©\©\©\©\
On Monday, May 10, 2021 3:35 PM, <klaas.reineke@...> wrote:
Yeah this fixes it, but then it does not help any more. I need the parameter/roll result passing to the Group as way to store a state. If I omit the %var2% it does not help. Here a more complex example to show what is needed. It is working from the state but the Error mesage is messing up the result window.
The code below is preserving the state that is changed for each call. The display text remains the same, i.e. "1". The group "other_1" can perform some calculation display the result via Msg or InputText and preserve state with the new call to Generate. If you click the 1 more the once the message within the messagebox does change correctly. I just need Tablesmith to not write an error for working code. I guess this is the boundary of the design of Generate.
%var1%,
%var2%,
:Start
1,|var1=1|
_|var2=2|
_{Generate~0,%var1%,~other_%var1%=%var2%}
:other_1
1,|var1=1|
_|var2={LastRoll~}|
_{Msg~%var2%}
_|var2+1|
_{Generate~0,%var1%,~other_%var1%=%var2%}
