Here is more information on the naming thing.
In the picker file, Each button has an id, like selectButton5, commandButton23, etc.
The id is guaranteed to be unique for a certain button, and it stays unchanged as long as the button still there so when you use MGPickerItem command API, you need to feed in an id string.
However, hard-coding id for API calls is not flexible, it won't work if you delete the button and recreate one, and it can only stand for one button. That is where the name property comes into play.
You can select multiple buttons in the view, and name them with the same string:
so that later you can use MGPickerView -getIdFromName "name" to get the list of button ids with the name.
In API point of view, a name is like an id for a virtual group and it avoids the hard-coded button ids in MGPickerItem calls.