🚀 go-pugleaf

Thank you, I have used the WaitForSingleObject function and
this works fine !!
Now my app is vefy fluid, after a small tune of the delay time
now the application is ok!

Thanks.
Fabio

J�rg Reithaar wrote:
> Hi
> 
> Your thread consumes too much resources because you requested it to do so.
> It checkes for incomming data at maximum speed....
> 
>     while ((!this->Terminated) && (objSerial->InstanceActive))
>     {
>        if (this->CanReceive) Synchronize(ReceiveData);
>     }
> 
> This makes your pc to become sslllooooooowwwww.
> 
> You have to add a "delay" into this loop.
> 
> // declare a variable as follows...
> 
> HANDLE hSemaphore;
> 
> // ...then add the following into the infinite loop
> 
> hSemaphore = CreateSemaphore( NULL, 0, 10, "X" );
> WaitForSingleObject( hSemaphore, 30 );
> 
> Resulting code:
> 
> while ((!this->Terminated) && (objSerial->InstanceActive))
> {
>    if (this->CanReceive) Synchronize(ReceiveData);
>    hSemaphore = CreateSemaphore( NULL, 0, 10, "X" );
>    WaitForSingleObject( hSemaphore, 30 );
>  }
> 
> Some explanation:
> 
> Windows is not preemptive. Task do not "suspend" automaticly to give others 
> a chance to execute in paralell.
> Thread programming is very near to system an should respect some rules to 
> execute smoothly.
> Do nothing more than absolutly necessary inside the threads EXECUTE routine.
> WaitForSingleObject consumes no time-resources because it realy suspends 
> execution for the time given.
> 30 in this case means 30 milliseconds. This time is a minimum. The systems 
> resumes not before the time given.
> 
> In gereral: Avoid to use endless loops inside the thread. Try to leave the 
> thread "sleeping" as much as possible.
> Just "kick" it on when you expect a delayed action.
> 
> Please let me know of your success
> 
> J�rg Reithaar
> Reithaar Elektronik GmbH
> 
>