A cautionary note:
DT Pro makes very heavy use of the Mac technologies built into OS X. DT Pro has a great many commands and routines that make calls to the operating system – many more than the ‘average bear’ Mac application.
If OS X code that’s called by DT Pro has been altered or damaged, problems will result.
But there are a great many applications and utilities out there that deliberately modify the operating system, including haxies and some input managers. Some of them are toys, like ShapeShifter, which changes the appearance of OS X. Others modify or add-on features to the operating system. The problem is that all too often there are unintended consequences that result in memory errors or even in breaking portions of the operating system. When that happens, routines called by DT Pro can fail, or errors can occur and cascade, or data may be corrupted.
My practice is to avoid installing anything on my computer that modifies the operation system, unless I’ve got an essential reason for doing so and I’ve thoroughly checked it out to be sure that it’s not going to cause problems. I avoid haxies and third-party input managers like the plague.
And I do routine preventive maintenance of my operating system and disk directory, to keep them in good shape. I don’t have damaged fonts. I clean out old caches fairly often, to minimize problems that could result from damaged caches.
As a result, I don’t have stability problems with my databases. I haven’t had to resort to a backup in more than two years. When I run Verify & Repair I don’t see error reports. I don’t lose data, and DT Pro “just works”. But I religiously make backups, anyway.
So, is DT Pro more “sensitive” to altered or damaged code in the operating system than most Mac applications? Only in the sense that it makes more calls to OS X technologies than, for example, a word processor or spreadsheet program is likely to make – but other programs can be affected, too.
Moral: try not to monkey with your operating system; keep it clean. Apple probably engineered the operating system code the way it is for good reasons. They’ve got procedures for testing OS modifications that far exceed the capabilities of most third-party developers, including extensive internal and external beta tests.