Part of WB-477: Orthogonal viewing has been fixed but there are problems with oblique viewing now.
oblique volume slice drawing is improved for volumes that do not have a voxel at the stereotaxic origin
Fixed volume slice outline for newer oblique volume drawing.
Removed print statements and restored cubic interpolation in oblque volume slice drawing.
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.
A bit more cleanup on  WB-477.
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.
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.
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.
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.
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.