Hi Amro,
thanks for your applause.
But I think you don't see the great benefits of that (mine) solution vs. your clustering. You could make the code I posted a SubVi with the reference array as an input. So you can drop it for any FP in your app without much (re)coding. And this I would guess is really usefull, cause logging (as posted in the first request) is very important to debug apps after shipping (so ctrl.X is pressed in status Y and error Z happens, finding that really nasty race condition a year after development....).
Second is, that in the first post, the name of the control was mentioned, thats why I chose that property from the list. You could use any other property (e.g. only boolean controls are of interest) to filter the events. Putting all into a cluster will always add the nessecity to have a comparrison algorithm, which of the elements changed. For me, this is an important increase in flexibility to *filter* what to log.
I used that trick for a bigger app (it contained about 30 XY-graphs) when I had to add additional functionality to these controls. Yeah, I live pre-XControl, but changing all ctrls to the appropiate XControl is even more coding than drop a VI and a property node on each VI. Ok, I now get philosophical as the evening gets late. But the power to control our FPs dynamically is often underestimated (and therefore LabView is underestimated).
And least: with the idea to do it, took me 5 min to code. And 5 min of fun. Bringing 120 Ctrls into a cluster and fixing the broken code, no fun.
Good night.
Felix
