Anderton
I'm not into mapping tons of parameters to controls on a permanent basis, because I can never remember what maps to what. So I don't use ACT the way it's supposed to be used, but I believe how I use it - as basically a variable "scratchpad" for parameter control - is simple, effective, and very close to foolproof once it's set up.
I have published the link to even more effective "scratchpad" solution. Touch parameter - you can control it with your knob, if you want "assign" it to some knob - press one button on surface, done. No ACT Learn mode, no confirmation dialogs. One button pressed - control assigned. Scalable to any number and type of controls, easy to add coarse/fine switch, indication on encoders, parameter name on controller display, etc, etc.
But I understand more and more that in this forum (shifted or not) most people just want SPEAK about something. I do not claim that all do that, there is tons of interesting information, solutions, workarounds, ideas. But this thread is an example of what I mean.
One wants exactly 4 clicks to assign any parameter and is not going to accept anything else. Other try to combine one surface with plug-in for another and wondering that does not work well (and once pointed the approach looks a bit strange, reply that any attempt to turn him from that windmill fighting is useless). The third, after an explanation that underling technology is not changed yet (but can be extended soon) still propose rewriting. Does some of them really wants something working? It does not look so for me.
So I surrender one more time. I see that my arrows do not even scratch that stone wall.