Event priorities

[mykaitch]

I have a DOH moment. If you write a tight loop under a button (say) you cannot click the button because the system rupts will not give you time ( try a while true loop for example). There is a Borland 'command' to force the loop to test for rupts such as mouse click or keyboard, but I have forgotten what it is !!! As a result my (very fast app) runs but I cannot click my end button. Anybody remember the command/method please ?

 

[tsh73]

try
Application.ProcessMessages

 

[itsgsd]

I think you want Application->ProcessMessages();

 

[itsgsd]

tsh73, looks like we posted at the same time... great minds and all.

 

[mykaitch]

I hope this is the right place! Yes, thanks, that worked okay but much better I found was to put the loop in a thread and then it runs in the background whilst I do all the pretty stuff.

 

[TonHu]

Even when spawning off a thread you should be a 'good citizen' and allow for other processes on that processor, to get a little attention from it, by releasing some spare cycles to them by ProcessMessages() You'll hardly notice any downgrade in process-speed, but the entire system will be _much_ more responsive!

HTH
TonHu

 

[mykaitch]

Thanks for that too, I will put it back in my thread stuff.