public class FatalError extends org.freedesktop.bindings.FatalError
By definition, a
CRITICAL has to be fatal; the application is
known to be in an undefined state after one has been emitted. While some
programs allow the user to carry on in blissful ignorance, these warnings
indicate a programmer doing something wrong, and that needs fixing.
The message has, therefore, been thrown as a Java Error. This gets you a stack trace at the place where the problem occurred, and that's how we identify problems in the Java world.
This is not the wrapper around
This class is our way of exposing fatal error conditions in a
GError, on the other hand, is GLib's
mechanism for returning conditions that the developer can ask the user for
a decision about. Incidentally, we do not expose those directly in the
java-gnome public API; where they occur we propagate an appropriate Java
checked exception instead. See
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString