Hello Markus,
> I know that this is bad design, but that is used only for testing the dll
> Later it will be replaced by another dll which really will be event driven
First of all, writing event driven is in fact more simple that
sequentional programming if you are used to do it. Secondly you are
> > I know that this is bad design, but that is used only for
> testing the dll,
> > nothing more. Later it will be replaced by another dll which
> > really will be event driven. For simple
> > test purposes such a complicated event driven app.
> > would be overkill!
>
> You are loosing your time
> > The app. does something like this:
> >
> > repeat
> > send something;
> > wait some ms;
> > until ende = true;
>
> This is bad design considering you are using an asynchonous
> component. You must replace any loop by
> a cascade of events. Just like any normal GUI program: you
> have a r
Hello Markus,
If you call the message pump, then depending on who called your code,
your function can be re-entered. For example if the caller himself comes
from the messagepump then it can be calling again if message in queue.
Most of the time pumping messages in code is a bad idea and should no
> -Ursprüngliche Nachricht-
> Von: Francois Piette [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 3. Mai 2005 13:56
> An: ICS support mailing
> Betreff: Re: [twsocket] Messages
>
>
> > does a sending TWSocket need to have its messages processed?
>
> Yes, it have to.
>
> > If yes how
