🚀 go-pugleaf

This was my problem, named objects:

    // create event and store handle
    MyEvent = new TEvent ( NULL, false, false, MyName );

I've changed it to:

    // create event and store handle
    MyEvent = new TEvent ( NULL, false, false, "" );

This is why running the application twice caused problems, as signaling in 
one app was causing the threads in both apps to wake up (when one wasn't 
supposed to).  I hope this is correct?

Is there an easy way to have named objects which are unique, such as using 
the process ID?  Is there an impact to the OS in having too many? (wrong 
forum I know).

Paul


"Paul at NCF" <not plmacca@clara.co.uk> wrote in message 
news:44d1a7a0$1@newsgroups.borland.com...
> Hi,
>
> It appears something has gone badly wrong with my framework, it doesn't 
> seem to be anything to do with UDP or Indy components.  I've run my 
> framework test harness, and again with two instances running, it locks up 
> and hangs. It never use to do this.  Time to get my backups out of SCM and 
> find out whats changed.  I might do the same test on another machine and 
> make sure its not my BCB install thats at fault too.