On Wed, 26 Oct 2016 20:23:11 +0200
Sascha Hestermann via Lazarus wrote:
> Am 26.10.2016 um 12:02 schrieb LacaK via Lazarus:
> > Btw. when TTimer is executing OnTimer method, which does not finishes
> > until next Interval is elapsed, is again called OnTimer ? Or
Dňa 26.10.2016 o 11:17 Michael Schnell via Lazarus napísal(a):
On 26.10.2016 07:57, LacaK via Lazarus wrote:
procedure TRefreshFileListThread.Execute;
begin
while not Terminated do begin
Synchronize(@MyForm.UpdateFileList); // UpdateFileList is method
which clears listbox and then adds
Big Thanks to all. Now I understand what is happening ... probably I wil
use critical section to block access from thread when code in main
thread is performed ...
-Laco.
ShowModal() for a modal form will call it.
[...]
I did test in Delphi and Delphi seems also perform synchronize upon
ShowModal() for a modal form will call it.
Ah really?
It happens in my application!
Then that is your problem.
:-)))
But is it correct behavior ? IMO it is against thread safety, which
should Synchronize guarantee!
The two issues are completely unrelated. The current behaviour is
On Wed, 26 Oct 2016, LacaK via Lazarus wrote:
Check for Application.ProcessMessages and CheckSynchronize calls.
These process synchronize queue, if I am not mistaken.
I do not call CheckSynchronize nor ProcessMessages in my application.
So only any LCL component or widget set can call