csCreating not used

[zex2011]

I don't understand why is csCreating not used in LCL. It is declared and never used. Often during creation I want to know (inside another method) whether it was called from constructor or another code. How do I know if a component is just being created or not?

For destroying I have csDestroying in ComponentState, but for creation there's no indicator. Please no advices like "do it yourself every time in every component you make".

[JuhaManninen]

I don't understand why is csCreating not used in LCL. It is declared and never used. Often during creation I want to know (inside another method) whether it was called from constructor or another code. How do I know if a component is just being created or not?

For destroying I have csDestroying in ComponentState, but for creation there's no indicator. Please no advices like "do it yourself every time in every component you make".

I guess csCreating was not needed by any of developers and it was not considered important.
It may also be difficult to implement. How to know when the constructor finishes? Maybe Delphi has some compiler magic involved.

csCreating and ControlState are in TControl. For TComponent you have also csLoading etc. which are used a lot in LCL, although it is not the same as csCreating.
I am thinking what kind of problems you would solve with csCreating?

Juha

[zex2011]

Some things related to refreshing the screen don't work properly when called from constructor (while the control is still being created). Ok, never mind. Your point is valid... how to know when the constructor is over. I guess I'll have to implement the flag myself.

[JuhaManninen]

Some things related to refreshing the screen don't work properly when called from constructor (while the control is still being created).

Setting visual properties of controls is allowed in a constructor (IIRC). The problem only is that they don't show immediately, and if there is a time-consuming initialization then the app seems like frozen for a while.
One good solution is OnIdle handler for slow initialization. OnIdle gets triggered only after the form is shown and you can show appropriate status messages etc.
It is used in Lazarus code in many places. The latest I added was the new Example Project Manager window (ManageExamples.pas).
You could copy the idea and some code from there or from other similar places.

Juha