Resolve/Fix WB-470: When overlays are yoked, the enabled/disabled status is only applied if the same file is in another yoked overlay.  The enabled/disabled status does not change the enabled status of a different file with the same yoking.

Reopen WB-470: Disable yoking of overlay enabled status since it is only supposed to take affect for the same file.

Resolve WB-472 Improve Help Searching: Search command limited listed hep pages to those containing the search query.  However, if a parent item did not contain the search text, its childen were not displayed even if one of the children contained the search text.  There are now two sections on the Help Dialog: Table of Contents that contains the help hierarchy and Search that contains all commands in alphabetical order with a search text box.

Resolve WB-470 Add On/Off Status of Layer to Layer Yoking Functionality: The enabled status is yoked with the selected yoking group.

For WB-471 Reload Layer to Constructor Dropdown: Update any visible overlay and map settings editors since they may contain the file that was reloaded and its palette may have been modified.

QGLWidget::grabFrameBuffer()  on Mac appears to grab the 'back buffer' so when capturing an image, call QGLWidget::grabFrameBuffer() twice to fix image capture.

When a scene is restored, close any overlay settings and palette map eidtors since the files they contain may no longer be valid.

Changing theshold values was not triggering PaletteColorMappings modified status.  As a result, scene creation  not adding the modified palette status and thus scenes did not restore correctly.

WB-405: Fix synchronization of thresholding sliders and spin boxes.  Update tooltip for threshold link checkbox.

Fix a few items on Map Palette Settings: (1) Fixed step value set to 1% of data range for 'Fixed' spin boxes; (2) Added step value set to 1% of data range for threshold spin boxes; (3) Threshold slider were not enabled when 'Unlimited' range.

Added numeric value into menum items for setting min/max thresholds with right-click menu on histogram.

new -cifti-stats and -cifti-weighted-stats commands, new method in mapping types to get an index's name, some minor fixes

(1) Move the code that converts an image size to a 'standard units' string from CaretDataFileHelper to FileInformation. (2) Show the uncompressed image size on the Image Capture Dialog.

Bug Fix: If image capture failed, the graphics state, prior to attempted image capture, was not properly restored.

Implement part of WB-405 Easier options for setting of palette thresholds: If thresholding is enabled, the user can right-click the mouse on the histogram plot that results in a menu popping up that allows the user to set either the low or high threshold using the X-coordinate of the mouse on the histogram plot.

Added WuQwtPlot that extends QwtPlot and adds a signal for display of a context sensitive (right-click) menu that includes the event and the X and Y-coordinates in the graph that correspond to the location of the mouse click.

remove try blocks from read/write functions of border and volume file, make VolumeBase more robust to exceptions during constructor

Updated CommandParser::parseComponent() so that it will catch a 'bad_alloc' exception and throw a DataFileException that includes the name and the size of the file.

Moved Brain::getBadAllocExceptionMessage() to the static method CaretDataFileHelper::createBadAllocExceptionMessage() so that other classes can generate the error message.

Added a catch of std::bad_alloc for Border and Volume File reading since their read method was catching any exception with 'catch (...)'.

Added catching of a bad_alloc exception in CaretDataFileHelper::CaretDataFileHelper::readAnyCaretDataFile() method and also a static method that creates a useful message for a bad_alloc exception.

Add try/catch for a std::bad_alloc exception when reading each type of data file so that a useful error message can be presented to the user in the GUI instead of calling the new handler and aborting wb_view.

Use CaretPointer for the dataArray member of GiftiFileSaxReader so that memory does not leak if an exception gets thrown while reading the data array (out of memory).

Function that set new and unexpected handlers has been split into one function for each of the handlers.  The new handler is no longer used in wb_view or wb_command so that a std::bad_alloc exception is thrown when operator new fails to allocate memory.

Removed exception specifiers from all methods.  By doing this, we can now catch a 'std::bad_alloc' exception when reading files within the Brain instead of unwinding to the uncaught exception function and exiting wb_view.

Add code in Brain's file reading to catch bad_alloc exception and any exception but it is not catching the exceptions.  Will try on another O/S.

Fixed memory leak in GiftiFileSaxReader.  The leak occurred if GiftiDataArray::readFromText() threw a GiftiException.  Now, when the GiftiException is caught in GiftiFileSaxReader::processArrayData(), the 'dataArray' is deleted.

When creating a scene, the user is notified if there are any files but CIFTI files were not being checked for a modified status.  This has been corrected.

Update to WB-421: When a user loads a file more than once (has the same name), the name of the file is modified to indicate the file is a duplicate and has a unique name.  When this happens, the files modified status is set which results in notification to the user when exiting wb_view or creating a scene.