Quote
Does this mean, in your opinion, that Threads cannot be used reliably in FireMonkey Applications?  Makes it not exactly ready for prime-time!

Quote from: Galfar on  1 June 2012, 12:08:42
Certainly seems like it. 

Well, that's disappointing, though not altogether surprising, I suppose.  Thanks for your thoughts on this slightly off-topic question.

Quote from: Galfar on 24 May 2012, 14:39:45
It happens sometimes, the problem is with TThread.Synchronize (TThread.Queue doesn't work at all) in FireMonkey app

Does this mean, in your opinion, that Threads cannot be used reliably in FireMonkey Applications?  Makes it not exactly ready for prime-time!

Quote from: Galfar on 24 May 2012, 14:39:45Where exactly do you mean? In Imaging core AnsiString and AnsiChar are for a reason (loading from files etc.) but warnings shoudl not be generated by Delphi. There are some warnings in JpegLib and LibTiff libraries though.

Yes, they were in those two latter libraries.  I assume I can safely ignore the warnings?

I've successfully compiled the firemonkey demo for Win32 under Delphi EX2 and when I open the file the progress wheel just goes around forever UNTIL I minimize and then restore the window, at which point the image appears.

Anyone else have this problem?

Also, there seems to be a mismatch between Strings and AnsiStrings in a number of places.  Was this deliberate or can I safely replace all the AnsiString and PAnsiChar with String and PChar?

Thanks!