'last (sw)' bug

[tester]

Why is this happening?

And why this helps?

[Nubeat7]

things like this only can be found by you tester

this only happens with arrays, btw, why you want to trigger the other in of the last switch when updating the value?

if you want to update it manually or from other triggersource its better to use a s&h
if i understand your schematic right you wanna do this

[Nubeat7]

what i could think is that the trigger from the node arrives while the array values on the other in of the last switch gets updated so that both gates are opened which ends up in adding the values?

[tester]

Like Trog - some time ago I started to like clean, compact, elegant solutions.

As for the schematic part - there is complex order of things happening:

1) block synchronized changing on slider
2) change "synced" list
3) change "crosscopy" value
4) trigger new crosscopy value - another little thing with few block/unblock nodes and trigger order things
5) change back "synced" list
6) change back "crosscopy" value
7) unblock synchronized changing

There are two items interacting with each other, and while both have independent "synced" lists - changes on one item affect elements on second item (single values inside array).

[KimSteff]

I must bee a bit slow!! What are the problem. Please explain ?

[tester]

What problem?

Ah, you mean what is the topic about. Two not related things. I found an error in FS regarding arrays, their triggers and "last" switch; just check the schematics. Then - Nubeat7 was wondering about general design I work on in context of using such trigger from array to set the switch. So I explained. As I said - two not related things.