1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Donation with Paypal!!!

    Go to your paypal account and send directly donation to [email protected]

    1 month - 10 $ - Standart VIP

    6 months - 20 $- Standart VIP

    1 year - 30 $- Standart VIP

    2 years - 50 $- Standart VIP

    Gold member for life - 150 $- Standart VIP

    High Vip (Standart VIP include) group please send PM or email to [email protected] for info

    After Donation please send email to [email protected]

  3. Donation Ways 2020


    Paysend
  4. Telegram
Dismiss Notice

Donation with Paypal!!!

Go to your paypal account and send directly donation to [email protected]

1 month - 10 $ - Standart VIP

6 months - 20 $- Standart VIP

1 year - 30 $- Standart VIP

2 years - 50 $- Standart VIP

Gold member for life - 150 $- Standart VIP

High Vip (Standart VIP include) group please send PM or email to [email protected] for info

After Donation please send email to [email protected]

Dismiss Notice
For open hidden message no need write thanks, thank etc. Enough is click to like button on right side of thread.

AfterCreate

Discussion in 'Delphi Programming' started by delphiy, Oct 31, 2015.

  1. delphiy
    Offline

    delphiy DF Member

    I need an AfterCreate in a Tobject because I need the MemoryStream to operate.
    If I had a component their must be a way to catch the state designtime/Runtime 

    But I have an object so I was thinking of using a thread with a sleep that will drive AfterCreate and destroy its self. And give a Boolean saying AfterCreate has run.

    Can you see any problems with this idea
    Should I use the thread to execute a message to run AfterCreate as a safer way to remove any conflicts.
    TApplication.Idile is an event little hard to reach I think and may get used twice
    Using Delphi 7
     

     
     
    paramithas likes this.

Share This Page