Note the comment.<\/p>\n
The non-threadsafe part is the call to ShowMessage. Any update of the UI should be done from the main thread.<\/p>\n
The quite reasonable question that followed after showing the code was “How would you make it threadsafe?”<\/p>\n
The correct but not very useful answer is to do the call to ShowMessage from the main thread.<\/p>\n
![\"Multi-threaded](\"http:\/\/www.malcolmgroves.com\/blog\/wp-content\/uploads\/2014\/12\/multithreadedtheorypractice.jpg\")
<\/a>Multi-threaded Programming. Theory vs Practice<\/p><\/div>\n
How? You have two main choices.<\/p>\n
Both involve wrapping your UI code up in an anonymous method. If you pass that\u00a0method to TThread.Synchronize<\/a>, it will be executed on the main thread and your task will block until it is finished.<\/p>\n If instead you pass it to TThread.Queue<\/a>, your Task will continue on running (or in this case, finish, as it is all done), and at some point in the future your anonymous method will execute on the main thread.<\/p>\n Which one you choose will be dependent on what you are doing. In general if I can avoid blocking I will, so if my situation allows it I use Queue for performance reasons.<\/p>\n If you’re looking for more details on the PPL, including some meatier examples, check out Danny Wind<\/a>‘s CodeRage 9 session, and stay all the way to the end.<\/p>\nprocedure TFormThreading.Button1Click(Sender: TObject);\r\nvar\r\n aTask: ITask;\r\nbegin\r\n aTask := TTask.Create(procedure\r\n begin\r\n sleep (5000);\r\n TThread.Synchronize(nil,\r\n procedure\r\n begin\r\n ShowMessage ('Hello');\r\n end);\r\n end);\r\n aTask.Start;\r\nend;<\/pre>\nprocedure TFormThreading.Button1Click(Sender: TObject);\r\nvar\r\n aTask: ITask;\r\nbegin\r\n aTask := TTask.Create(procedure\r\n begin\r\n sleep (5000);\r\n TThread.Queue(nil,\r\n procedure\r\n begin\r\n ShowMessage ('Hello');\r\n end);\r\n end);\r\n aTask.Start;\r\nend;<\/pre>\n