InstrumentLab for Visual C++ MFC

InstrumentLab is a set of visual instruments and controls based on GDI+. For Delphi / C++ Builder, InstrumentLab is a set of native VCL components, and these components can be composited.InstrumentLab is implemented using a very fast MMX optimized libraries to perform the plotting calculations, and is designed mainly for very fast real time data plotting applications, such as DSP, Audio Processing, Video and Image Processing. he InstrumentLab is a set of visual tools and controls based on GDI+. For Delphi/C++ Builder, InstrumentLab is a set of native VCL components, these components can be implemented composited.InstrumentLab using very fast optimized MMX libraries to perform plotting calculations, mainly intended for very fast real-time data plotting applications such as DSP, Processing Audio, video and image processing. The MFC is a class library that provides a collection of C++ classes, taking the drudgery out of writing software for Windows. The classes are targeted at the features your application needs – such as status bars, the implementations required for multiple document windows, and support for context-sensitive help – which means that using MFC saves you coding time which you can use to implement other features in your application.

MFC was introduced in 1992 with Microsoft’s C/C++ 7.0 compiler for use with 16-bit versions of Windows as an extremely thin object-oriented C++ wrapper for the Windows API. C++ was just beginning to replace C for development of commercial application software at the time. In an MFC program, direct Windows API calls are rarely needed. Instead, programs create objects from Microsoft Foundation Class classes and call member functions belonging to those objects. Many of those functions share their names with corresponding API functions.

One quirk of MFC is the use of “Afx” as the prefix for many functions, macros and the standard precompiled header name “stdafx.h”. During early development, what became MFC was called “Application Framework Extensions” and abbreviated “Afx”. The name Microsoft Foundation Classes (MFC) was adopted too late in the release cycle to change these references.

MFC 8.0 was released with Visual Studio 2005. MFC 9.0 was released with Visual Studio 2008. On April 7, 2008, Microsoft released an update to the MFC classes as an out-of-band update to Visual Studio 2008 and MFC 9. The update features new user interface constructs, including the ribbons and associated UI widgets, fully customizable toolbars, docking panes which can either be freely floated or docked to any side and document tabs.

MFC was initially a feature of the commercial versions of Visual Studio. As such, it is not included in the freeware Visual C++ Express. The Community edition of Visual Studio, introduced in 2014, however, includes MFC.

Object Windows Library (OWL), designed for use with Borland’s Turbo C++ compiler, was a competing product introduced by Borland around the same time. Eventually, Borland discontinued OWL development and licensed the distribution of the MFC headers, libraries and DLLs from Microsoft^[6] for a short time, though it never offered fully integrated support for MFC. Borland later released Visual Component Library to replace the OWL framework.

MFC is a library that wraps portions of the Windows API in C++ classes, including functionality that enables them to use a default application framework. Classes are defined for many of the handle-managed Windows objects and also for predefined windows and common controls.

At the time of its introduction, MFC provided C++ macros for Windows message-handling (via Message Maps ), exceptions, run-time type identification (RTTI), serialization and dynamic class instantiation. The macros for message-handling aimed to reduce memory consumption by avoiding gratuitous virtual table use and also to provide a more concrete structure for various Visual C++-supplied tools to edit and manipulate code without parsing the full language. The message-handling macros replaced the virtual function mechanism provided by C++.

The macros for serialization, exceptions, and RTTI predated availability of these features in Microsoft C++ by a number of years. 32-bit versions of MFC, for Windows NT 3.1 and later Windows operating systems, used compilers that implemented the language features and updated the macros to simply wrap the language features instead of providing customized implementations, realizing upward compatibility.

The MFC ribbon resource editor allows the developer to design the ribbon graphically instead of having to use the XML-based declarative markup like the RibbonX API. Optionally, ribbon components may be programmed directly by calling a new set of ribbon class methods. The developer may mix graphical and programmatic ribbon development as is convenient. The MFC application wizard has also been upgraded to support the new features, including a check-box to select whether the application will use the ribbon or the docking panes. The new functionality is provided in new classes so that old applications still continue to run. This update is building on top of BCGSoft’s BCGControlBar Library Professional Edition. Microsoft has imposed additional licensing requirements on users of the ribbons. These include a requirement to adhere to Microsoft UI Design Guidelines, and an anti-competition clause prohibiting the use of the UI in applications which compete with Microsoft Office.

COMPATIBILITY

At the very outset, DBI’s VP of product development – understood the value of engineering controls in C++, leveraging the MFC and GDI+ libraries offering superior overall performance required for the complex drawing routines of interactive ListView and TreeView controls, multi-sorting Calendars and Appointment Scheduling controls, UI Design and Timeline multi resource Scheduling controls. At the same time, incorporating portability across the many Windows based Integrated Development platforms.