[DUG] Compnent creation question

[Neven MacEwan]

Paul

Thats why I though a Items.BeginUpdate would suppress events on the strings
Usually as someon else posted, if this is a problem they may have a 
preceding event

Neven

> Rob wrote: 
>
>   
>> Sounds likely.  I am calling it BEFORE inherited destroy.
>>
>> Off home now.   hopefully all will fall into place in the morning !
>>     
>
> I just noticed you said it happens when you use the .Items property. So
> David Moorhouse is bang on (and succinct too!)
>
> The TStrings Wrapper is trying to talk to the COMBO control, by design.
> Obviously not supported in destructors. Bugger. The lifetime of Window
> handles against MS builtin controls are subtle and they are quick to
> anger.
>
> I'm somewhat surprised that the Window handle is already verboten before
> calling inherited like you're doing. Mind you, it might be a
> csDestroying 'prevent other even nastier issues' sort of thing.
>
> You'll probably need to eat your young before the Window handle is AWOL,
> or there may be a way to stop the TStrings wrapper from trying to talk
> to it's twin who's rotting in the grave already (to so speak :-)
>
> <insert toothless crone in gypsy shawl impersonation>:
> "I see a tall, handsome,.. I mean steaming chunk of VCL source code to
> read and step through (or in?) in your future."
>
> TTFN,
>   Paul.
>
> P.S. 
> Apologies to all for the whole bad horror fiction vibe. I have a short
> story first draft incubating in my subconscious for revision/rewrite and
> it just keeps lurching up and grabbing at me... Which is sort of good
> thing. Hrmmmph... I'll stop now.
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at delphi.org.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject: unsubscribe
>
>
>