No it is actually exactly that.
it tries to access the global TGraphics object to operate on it. As graphics is not called it is null -> null object access violation.
You can easily use Try - Catch - EndTry and creategraphics within to check if a given graphics mode was "setable" and react to the creation error yourself instead of assuming it works and assume that BM plays nicely if your app doesn't do its homework and error handling :D
it tries to access the global TGraphics object to operate on it. As graphics is not called it is null -> null object access violation.
You can easily use Try - Catch - EndTry and creategraphics within to check if a given graphics mode was "setable" and react to the creation error yourself instead of assuming it works and assume that BM plays nicely if your app doesn't do its homework and error handling :D