For a quick start:
	See 00_toplevel_example.sln for an example VisualStudio project.
	See 00_toplevel_example.pro for an example QtCreator project.


SUMMARY
===================
This folder contains source code excerpts from the TecellaLab application that provide Qt UIs for amplifier settings, per-channel settings, and the system monitor.

Example code for stimulus and acquisition logic is not included in this folder.  Please refer to the regular (Non-Qt) example code included with the TecellaAmp API instead.

LICENSE
===================
These excerpts are released under the MIT License, and are free for you to modify and use without restriction. See license details in the LICENSE.txt file.

NOTES
===================
Care has been taken to remove any dependencies on libraries other than the STL and Qt, so the excerpts should be usable in an existing Qt application unmodified.  The files are copied directly from TecellaLab unmodified, so any updates to TecellaLab will translate over automatically to these examples.

To use these UI widgets unmodified:

*** Implement stimulus and acuisition logic in your application.
*** Create a valid amplifier handle using tecella_initialze().
*** Create instances of the AmplifierSettings widget and the ChannelSettings widget. (The SystemMonitor widget is invoked by Amplifier settings and need not be created by your application directly.)
*** Call setAmpHandle() for both AmplifierSettings and ChannelSettings, so their UIs are updated with the proper scales, units, and feataures.
*** Connect the "acquisitionHint(bool acquiring)" slots of AmplifierSettings and ChannelSettings to your custom acquisition logic, so the proper widgets are disabled during acquisition.
*** Connect the "ampOrConfigChanged()" signal of AmplifierSettings to your application logic, so that your application can respond automatically to changes in the amplifier configuration (e.g. iclamp vs vclamp, units and scale of the response, stimulus, and registers.)
*** Part of your response to the ampOrConfigChanged() signal, should be to call setAmpHandle() again for ChannelSettings so that itcan update it's UI.
