mdLib / Q&A   Do you use any naming conventions?   Yes. All component names start with the letters 'TML' and all function or procedure names with 'ML_'. For unit names, we use the matching (were appropriate) unit name from the VCL, but starting with 'ML_'. For example, our TMLList (that inherits from TList) is in the unit 'ML_Classes' (where-as TList is in the 'Classes' unit).   Why is mbLib not showing on the component palette when I install a new version of Delphi?   The mdLib installer detects which versions of Delphi are present, and only installs the files relevant to those versions. If you install a new version of Delphi, all you need todo is re-run the mdLib installer.   We would like a custom component or routine developed, can you help out?   Most certainly, this is one of our specialities and we offer competitive market rates for such work. Please see the contact page for further details.   How will mdLib grow in the future and can I contribute?   mdLib is only a small collection of some of the components and routines that we have developed over the years. Periodically we will be adding new content in the hope that mdLib matures into a well used and diverse library. Whilst you cannot contribute directly please feel free to send us your (constructive) suggestions.   Will newer versions of mdLib be backwards compatible with older one's?   In the main yes, however, from time to time we may change parts that breaks backwards compatibility. Whilst backwards compatibility is more convenient, more often than not, compromises and workarounds have to be made that tend clutter code and the interfaces (Windows is a classic example of this). Our personal view is that, whilst these changes can be inconvenient, they don't happen that often and when they do they are well documented and fairly easy to change.