Scope's features are realized by

programming in C++ using Microsoft Visual Studio 2012
using modern C++11 features, STL, and Boost libraries
using the lightweight Windows Template Library (see scope::gui)
relying on Direct2D for displaying (see d2d)
using Windows Imaging Components for TIFF saving (see scope::ScopeMultiImageEncoder) and exiftools.exe for writing ImageJ compatible TIFF tags (see scope::StorageController::StorageControllerImpl::FixTIFFTags).
A pipeline of 'controllers' for data acquisition (scope::DaqController), assembling images (scope::PipelineController), displaying images and histograms (scope::DisplayController), and storing to disk (scope::StorageController)
classes for different hardware for sampling PMT input (scope::InputsDAQmx and scope::InputsFPGA), and FPGA classes (scope::FPGADemultiplexer, scope::FPGAPhotonCounterV2)
classes for different scan modes, until now frame scanning in sawtooth (scope::ScannerVectorFrameSaw) or bidirectional (scope::ScannerVectorFrameBiDi) mode and ETL plane hopping (scope::ScannerVectorFramePlaneHopper)
the ability to run all these controller for every area in a separate thread
implementing a custom set of thread-safe values (scope::ScopeValue, scope::ScopeNumber, scope::ScopeString) that can be connected to functions via Boost::signals2
implementing a custom set of thread-safe controls (scope::gui::CScopeEditCtrl, scope::gui::CScopeSliderCtrl, ...) to use underlying scope::ScopeValue.
extensive code documentation using Doxygen
version control through git and hosting at sourceforge.com

ScopeValues

A core component of Scope is the scope::ScopeValue class and its derivatives scope::ScopeNumber and scope::ScopeString. They provide thread-safe access to a data member. More importantly you can connect functions to these objects that are called when the data member is changed or when the read/read-write property of the object is changed. ScopeNumbers also provide range checking.

ScopeControls

Several classes derived from WTL classes encapsulating dialog controls. They can easily be connected to ScopeValues. Then the scope::ScopeValue is displayed in the control, edits to the control lead to changes of the scope::ScopeValue and vice versa. Also setting the read/read-write mode of the scope::ScopeValue disables/enables the control.

GuiParameters

The controller ScopeController has a static public data member scope::ScopeController::GuiParameters that contains a lot of scope::ScopeValues that describe all parameters of the current Scope configuration. By connecting ScopeControls to ScopeValues in scope::ScopeController::GuiParameters, this contains the values that are displayed/can be edited in the GUI.

Controllers

A set of classes derived from scope::BaseController, which holds a thread object and several member functions to start/stop this thread (using an scope::AbortCondition member). All these classes use the pimpl idiom to hide the implementation and shorten compile times. Each object has its own parameters data member. Derived classes like scope::DaqController mostly overwrite the Run method (which is run in the objects thread upon invoking the Start method).
SynchronizedQueue's provide data flow between the controllers (from scope::DaqController to scope::PipelineController to scope::StorageController and scope::DisplayController). They send ScopeMessage that contain different data types as cargo member (scope::DaqChunkPtr or scope::ScopeMultiImagePtr after the scope::PipelineController).

ScopeInputs/ScopeOutputs

These classes encapsulate the communication with the data acquisition hardware. scope::InputsDAQmx and scope::OutputsDAQmx utilize the National Instruments DAQmx C-API (through a thin C++ wrapper in the DAQmx namespace). scope::InputsFPGA uses the National Instuments FPGA C-API.