[jmarshall]

There's a reason for that (no setID): The controlgroup holds a speedup mechanism in the form of an ID -> control* map for the constant "get control with id <foo>" that gets done. If you go and change the ID, then you'll need to update that map, which means that the child control needs public access to that function in the parent etc.

When you create a control from python, one of the things you provide is the ID, right? i.e. do you really need a way to set the ID from python?

Cheers,
Jonathan