4.6 UI How to apply OnClick handler for button generated at runtime (script)?

Works perfect. Thanks! The lambda expression was confusing me in the other example.

@invadererik

In a statement foreach(string a in places) a is an iteration variable, which means that on every iteration of the loop it is assigned the next value in the collection you iterating over. In most cases it doesn't cause you any issues, because if you are executing statements immediately, so it is the right value. It shows it's true nature when a anonymous method is involved. A statement:

 b.onClick.AddListener(() => MyMethod(a));

doesn't actually execute MyMethod(a) it just adds a reference to it in the button b. Because all this happens before you can press any buttons, the loop would have worked all the way to the end constantly changing the value of a until it stopped on the very last element in the loop. (Normally a would be destroyed afterwards, but ins$$anonymous$$d it lives on because of the stored references in the buttons).

When a button is pressed it executes all the attached listeners and MyMethod is called with the current value of a. This makes sense, because you can capture and object and you are interested in it's state when the button is pressed (e.g. if ins$$anonymous$$d of a string we were talking about an InputField you would probably want to read the value of that field once the button is pressed and not the one it had when you were assigning the listener).

When you add a statement:

 string captured = a;

The current value that a is stored in the variable captured, because it is executed while the loop is working. A separate variable captured is created on every iteration, so it won't be changing its value every single time.

This changes in C# 5 Once Unity upgrades to C#5 this issue will disappear, the iteration variable will be a new one on every loop iteration.

I tried my best here to explain this. If you are really interested in how C# works, how it evolved and what are the gotchas I really recommend the book *C# in Depth* by Jon Skeet.

This also worked for me! It's strange that, when you run trough a foreach loop, only the last method with AddListener(() => MyMethod(value) is stored, and this simple work-around

      foreach (string a in places)
     {
     GameObject go = (GameObject)Instantiate(buttons);
     go.transform.parent = panel.transform;
     go.transform.localScale = new Vector3(1, 1, 1);
     Button b = go.GetComponent<Button>();
     AddListener(b, a); // Using the iterator as argument will capture the variable
     }
     // Outside of method running the above
     void AddListener(Button b, string value)
     {
     b.onClick.AddListener(() => MyMethod(value));
     }

makes the code behave as you expect. Thx !!

@EMOTION THEORY from what I gathered they don't show up there because Unity considers them separately from listeners added in editor. If you add a listener in editor it's known as a persistent listener, if you add it in code it's a non persistent listener. You can see those terms mentioned in the UnityEvent doc (which is what onClick is).

Not sure if there is an easier solution than writing own inspector that will show the non persistent listeners.

Thanks! Only the outside the method version seems to work for me. Awesome answer though.