Non-visual RTTI component?

[egsuh]

Is there any non-visual RTTI component? I want this to connect between frame/forms, so that I can minimize my code typing 

Of course, I can drop a visual component and set its visibility false. Just wondering whether there are any non-visual component.

[jamie]

DataModule ?

[egsuh]

Hi jamie,

Datamodule is not exactly what I'm looking for, but your single comment gives me a great insight. Multiple forms containing rtti controls may share single datamodule and published property so that any change in one form is reflected in other forms automatically. This is really great. I forgot what I was looking for exactly    I'll think over again. Anyway thank you for kind comment.

[jamie]

Controls/Classes that houses a TPersistent at the base of the classes have observers and observed where you can notify others
etc

 Just and idea, I use something close to it in an automation application, whereas other classes of the same can receive notification events automatically and vice versa.

[egsuh]

What I wanted is to put a non-visual RTTI controls in a form, with its TIObject pointing to other components. So I thought setting the Rtticontrol invisible. And I can set other codes within the setter of the property of the TIObject (like showing / unshowing or limiting values, etc. to other forms).

As an example, I put a (invisible) TTIEdit in Form1, whose TIObject/TIPropertyName points to DataModule1/AIndex. Here, I can set Label1 of Form2, TIEdit of Form3, etc.

But I found simpler solution. I can create the rtticontrols within the form with code, and do not assign patent to it. Then it's invisible.

[cdbc]

Hi
Why not just use unit 'TypInfo', write the rtti-code yourself and the use the 'Observer-pattern' for the notifications?!? It's not /that/ complicated...
Just saying my 2 cents worth...
Regards Benny

[egsuh]

Why not just use unit 'TypInfo', write the rtti-code yourself and the use the 'Observer-pattern' for the notifications?

Simply I don't want to learn any more

[alpine]

As an example, I put a (invisible) TTIEdit in Form1, whose TIObject/TIPropertyName points to DataModule1/AIndex. Here, I can set Label1 of Form2, TIEdit of Form3, etc.

Only after a few days you'll wonder "from where the hell was that changing from?". I have that experience with the C# data/property bindings. But it is your call, actually.

[egsuh]

As an example, I put a (invisible) TTIEdit in Form1, whose TIObject/TIPropertyName points to DataModule1/AIndex. Here, I can set Label1 of Form2, TIEdit of Form3, etc.

Only after a few days you'll wonder "from where the hell was that changing from?". I have that experience with the C# data/property bindings. But it is your call, actually.

Yes.. I'm little afraid that. But trying to make regular pattern. Thank you for your comment, and please keep advising me. I'm trying several methods.