Can TObjectInspector handle frames and the contents?

[vfclists]

I am using the ObjectInspector/ObjecInspectDialog component to locate objects for editing in the PropertyInspector at runtime. It seems that it cannot locate components within Frames, although the one in form designer at design time is capable of doing so.

Is there anyway of working around that limitation?

[Thaddy]

Well, frames are a design-time only container by concept.
At compile time the parent form becomes the owner of the controls and the frame isn't there anymore...
If you need a reference at runtime you should use separate forms instead of frames.

[taazz]

Well, frames are a design-time only container by concept.
At compile time the parent form becomes the owner of the controls and the frame isn't there anymore...
If you need a reference at runtime you should use separate forms instead of frames.

erm no they are full containers, they are designer aware containers ee they can be floating windows while design but they are full blown containers on runtime just like a panel.

[Thaddy]

I wrote "by concept". That they behave like that is implementation detail and not guaranteed to be valid.

[balazsszekely]

@Thaddy
I told you, you're wrong about the frames! 

[taazz]

I wrote "by concept". That they behave like that is implementation detail and not guaranteed to be valid.

Who's concept? As far as I understand all controls under the frame are invisible that can't be achieved with "virtual" containers also setting the visible and enabled properties should also set the contained controls properties etc. I would say that frame are implemented to the concept of a container to perfection.