Closed for Company Meetings: Between September 18 (5pm PDT) and September 22 (12pm PDT), Support and Sales requests will be delayed. Only time-sensitive issues will be addressed during that time. Thanks for your patience.
Thank you again for your help. I used your patch to figure out how XOR works. It helped a hell of a lot to understand how a checksum is created.
Unfortunately, because of the way it is built, I can not get it to work. I need to add the XOR checksum to the list. And I tried a few tricks but I just can not get the final XOR checksum to be in the same list as the original list. It only gets the XOR before the last number is processed.
Mainly the problem is like this:
"Start patch and then stop. Once it settles, the number in the message (A) should be the same as the last numer in the list (B). But they aren't. The last numer in the list is actually the penultimate XOR that was calculated, and not the last one as it should be. Check the Max window for details."
Now I realised something. Does using encapsulating switch the priority of the messages going to append object? Kinda like saying "wait for the encapsulation [p] to finish processing and then send another list from [trigger l l] to [append]? Otherwise if it wasn't encapsulated I would have had the same problems with the resulted XOR being out of place (the penultimate instead of the last one)?