Hello,
thank you for your advice - sorry, it's not easy as a beginner. Please, please. Be kind and patient to us newbies. I know how hard it is as a professional to read all that dumb stuff. But everyone has to start somewhere and take all of the hits, too, until they know better.
All of your solutions - using shift registers, using the CtrlRef, using the NewVal, OldVal or other elements of the event structure - i already checked them out long before and took them in for a reflection on how to solve the problem.
I think (maybe it's just me who doesn't know better) that using multiple cases such as "All Elements Value Changed" won't help me out here. I've tried that already - and the only information i get from the "CtrlRef" element is "Cluster ###" - but i need the ref of the specific single control element from inside the cluster. That's why i needed to prepare the event structure to react on all those single elements. This leads inevitably to the fact that i can't use "OldVal" or "NewVal" either, because when using event cases reacting on single control elements within a cluster, easily to follow i only get only one specific value (the one that was changed last). However i need the whole cluster data to feed that SubVI. Surely i could disassemble and re-write it so it would loop simultanely instead of being executed once upon request, keeping constant data in internal shift registers and only registering changed data, but the use would not compensate the efforts, this is not speed relevant and it would get more complex for third party users with little experience to understand what's going on in that - really - tiny application.
And, to relax flared tempers, i already arranged a little conversation to learn more about local variables, property nodes and efficient design soon. So at least , no more dumb questions about this topic, at least not from me. At least i hope so.
Thanks.
