Posted by jpluimers on 2016/02/14
Posted in Delphi, Delphi 1, Delphi 2, Delphi 2005, Delphi 2006, Delphi 2007, Delphi 2009, Delphi 2010, Delphi 3, Delphi 4, Delphi 5, Delphi 6, Delphi 7, Delphi 8, Delphi x64, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Delphi XE6, Delphi XE7, Delphi XE8, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2016/02/13
Seems they got only released just yesterday because of the QA effort taking a long time. But it’s good news for Delphi/Rad Studio/C++-Builder Update Subscription members: some fixes are now back-ported to 2 Delphi versions. Which is a new milestone in support from Embarcadero.
Note that the list of fixes is at the bottom of these pages:
Posted by jpluimers on 2016/02/11
I must clean out my closets as well. I think I have similar stuff lying around.
Posted by jpluimers on 2016/02/04
I wrote about this before, named it a cardinal sin too, but I seem to have to repeat this:
When your product thinks the license is validate and quits without allowing the customer to save its work, then you’ve committed a cardinal sin.
For me it is OK if a product checks for binaries that do not to the product (and not signed by the vendor) in the product directories and fails to start, or to present a nag screen that takes a while to disappear, or even to limit functionality.
Given some recent posts and the fact that over the course of 10 different versions I lost days of work and at conferences I usually get multiple questions from people having suffered from this, I really had to bring this up again.
Posted by jpluimers on 2016/02/03
A while ago I bumped into this: As of Windows 7 (and probably Vista), the standard Windows Common Item (Open and Save) Dialogs expect the main thread to be initialised with STA because it is easier to support apartment threading in single-threaded apartments because COM provides synchronization on a per-call basis and the Windows GUI APIs are not guaranteed to be thread safe.
Windows XP and Server 2003 didn’t enforce this for the classic Windows Open and Save Dialogs, so it only appeared when the software below got run on Windows 7 in a way too late time frame (but the market share of XP is still high).
The reason is that when using Delphi, the TOpenDialog and TSaveDialog will use the classic Open and Save Dialogs on Windows < Vista and fall-forward to the new Common Item Dialogs handled by TFileOpenDialog and TFileSaveDialog (both will not fall backward).
When you have your COM initialisation done wrong, your application appears to hang. Amidst the plethora of threads started by the COM subsystem, these two dead-lock:
Posted in Delphi, Software Development, Development, Delphi XE2, Delphi 2007, Delphi 2010, Delphi XE, Delphi 2009, Delphi XE3, Delphi XE4, Delphi XE5, Delphi XE6, Delphi XE7, Delphi XE8, Delphi 10 Seattle | 2 Comments »