> You'd also need a counter for the handler, in case more than one designer is using it.

For now each class in a designer get's it's own handler, it may be okay to use one handler multiple times.
It's just that by switching from one designer to another Aselobj(...,1) does not return the object still open in the inacive designer and therefore the reference ID is removed, like when closing the designer. Still works, each designer activation causes the reference ID to change and the creation of a new eventhandler.

I plan to add observation of Aselobj(...) additional to Aselobj(...,1). This way you also get object references to subobjects, eg a container in a form class. And finally it would be great to handle multiple selection and eg change width of a group of labels at once, like you can now only via the property window.

Bye, Olaf.