Had mistakenly modified ApplicationInformation.cxx instead of ApplicationInformation.cxx.in.  Maybe we should consider generating a new header file with info instead of the cxx file.

Help resolve WB-483 - Workbench hanging with a specific file: During testing, it was found that the file contained some invalid values (infinities and/or not-a-numbers) causing computations to produce invalid values and ultimately causing the failure of a loop termination.  Code was added to detect this failure (in chart processing) but there was no good way to inform the user of the problem.  The new event EventAlertUser is now used to convey the problem information to the user.

Added a new event, EventAlertUser, that is used to alert the user to a problem and is in the Common module so that it is accessible to all other modules.  When this event is sent, EventManager will query the Application Type.  When the Application Type is a GUI application, the event is propagated like other events and will be received by the GUI manager which will then displayed the alert's information to the user in the GUI.  If there is not a GUI, the alert is logged at the severe level.

Added 'ApplicationTypeEnum' that defines the type of application (command line or GUI).  The application type is a static member in the class ApplicationInformation since this class is in the Common module and thus accessible to all other modules.  The application type is now a required parameter in the SessionManager's constructor so that the application type is properly set and this constructor then sets the application type in ApplicationInformation.

When the range for cartesian labels range is being created, test the 'end label' value for an invalid value (infinity or not-a-number) that will occur when the file contains invalid values.  When this situation is encountered, do not create the chart and log a message at the severe level alerting the user.

Partially resolve WB-477.  The problem is fixed for orthogonal slice viewing.  Howevere, oblique drawing may require a redesign so volume centering is not fixed for oblique viewing.

oblique volume slice drawing is improved for volumes that do not have a voxel at the stereotaxic origin

Resolve WB-478: If the selected file in an overlay is yoked and this file is removed, reset overlay yoking status to OFF.

Initial implementation of WB-429 Enable opening of image files and viewing as underlay in selected tabs

reinstall one change the was part of a recent reverted commit: Fixing 'file not found' errror message so that the file name was visible in error message dialog when the file had a very long path.

Fixed bug with newer volume quad slice drawing.  The Y-slice coordinate was off by one voxel causing volume surface outline to appear in the wrong position.  Turning on/off quad drawing on the Develop menu also displayed the problem.

Revert "Add an item to the Develop Menu ("Volume View Initialization at Center") that enables new functionality for defaulting the view of a volume.  This new functionality fixes the default view of volumes that do not contain a voxel corresponding to the stereotaxic origin (0, 0, 0) but it does cause issues with other volumes."

This reverts commit 1ab7cd39.

Having to remove changes for volumes without a voxel corresponding to (0, 0, 0) as the changes needed are much more complex to avoid breaking any and all types of volumes drawing including oblique drawing.

This reverts commit f68a72d7.

Having to remove changes for volumes without a voxel corresponding to (0, 0, 0) as the changes needed are much more complex to avoid breaking any and all types of volumes drawing including oblique drawing.

Add an item to the Develop Menu ("Volume View Initialization at Center") that enables new functionality for defaulting the view of a volume.  This new functionality fixes the default view of volumes that do not contain a voxel corresponding to the stereotaxic origin (0, 0, 0) but it does cause issues with other volumes.

Moved a couple of computations outside of loops in volume slice drawing which seems to yield a slight improvement in performance.

Profiling was performed on volume slice drawing.  When colors were obtained for the voxels, the data in the corresponding map was requested so that if label data was being colored, the on/off status could be checked to to "turn off" coloring for the voxel.  The call to getMapData() was being made for all volume types but only needed for label volume types.  Now, the call to getMapData() is made only if a label volume is being colored and for non-label volume, performance is improved.

some cleanup in -zip-*-file: check return values of reading/writing, move buffer off the stack, stop using 1024-flavored units and simplify logic

CiftiMappableDataFile was calling CiftiFile::getCiftiXML() and assigning the returned value to "const CiftiXML".  The "&" for reference was missing and causing the copy constructor to be called.  The reference "&" has been added to avoid calling of the copy constructor.

Resolve WB-475 - Allow medial wall to be filled while other label entries are outline.  GiftiLabel was changed so that a function is always used to set the name of a label.  In this function, the label's name is examined to determine if the name is a medial wall name (name contains the text "medial" followed by zero or more characters, followed by "wall").  If it is a medial wall name, a flag is set and the flag can be queried.

Initial implementation of WB-475 (and WB-465) Allow medial wall to be filled while other label entries are outline.  First step was to move the properties from Features ToolBox->Labels->Attributes to Overlay and Map Settings->Labels.  In essence the label drawing type (filled and/or outline) and outline color are changed from Tab/Yoking Group properties to File properties.  Second step added a checkbox that enables filling of the medial wall (if its name is "MEDIAL.WALL") regardless of the Fill/Outline selection.

Use two argument constructor for DataFileException(filename, msg) to resolve WB-436, eliminate long error messages by placing the filename, path, and message on separate lines when the error message is displayed.