When a component is created at runtime is not given a name how can it be found?

[Joanna]

So after the properties are changed I’m assuming that the new properties will be saved in an inifile Or xml file for next time the program is reloaded?

[Thaddy]

no they should be saved in lfm or dfm format. Does not matter too much. It is just a format.

[Thaddy]

That is called persistence. Format does not matter.....

[Joanna]

@thaddy isn’t the running program using an exe file not lfm file though?
If he is using an object inspector  to change properties at runtime.

[vfclists]

@thaddy isn’t the running program using an exe file not lfm file though?
If he is using an objector to change properties at runtime.

Yes. The program is a running executable whose properties are changed at runtime using the object inspector.

The state of changed properties is labelled then saved in LFM format to a file or a database record to be loaded when required.

The object inspector (substitute) is useful when changing a lot of the properties is envisaged by an expert, but in practice only a few of them are changed, and when it is for use by end users, an dedicated interface which works on only the necessary properties should used.

For instance if you enabled an end user to set the Top and Left properties of a control, you wouldn't enable them to set them to negative values, change the Visible property to false.

[Joanna]

I never knew that was possible, I use inifiles for everything.
How do you implement saving to an lfm file within the program?

I’ve opened many .lfm files but I never saw much besides maybe position and the nesting of controls . It didn’t show all the things that would be in object inspector such as fonts , colors. Styles etc.

[cdbc]

Hi
@Joanna: Have a look here: https://www.freepascal.org/~michael/articles/ Scroll down until you see "RTTI for beginners" and download the pdf...
That's a nice little 'Treasure Trove' for you 
Regards Benny

[Thaddy]

handle. not name,

[Joanna]

Thanks for info