Custom Exception Class Triggers Tk Messagebox #1121
Description
As discussed in #1119, we could create a special class of exceptions. We could initialize these at the base layer for each device class, or even possibly every base class could inherit an exception type which bubbles up to the model and then directly informs the user of the problem. Each exception would require an informative message prompt.
We do not want this called all the time, such as when we have the NI DAQ exceptions that we automatically handle. But rather, when a preventable configuration-based error occurs.