Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!marktwain.rad.sgi.com!linton
From: linton@marktwain.rad.sgi.com (Mark Linton)
Newsgroups: comp.windows.interviews
Subject: Re: How to check that Bitmap is valid?
Message-ID: <1991Apr15.153520.16312@odin.corp.sgi.com>
Date: 15 Apr 91 15:35:20 GMT
References: <9104121357.AA03653@control.lth.se>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: linton@marktwain.rad.sgi.com (Mark Linton)
Organization: sgi
Lines: 15

In article <9104121357.AA03653@control.lth.se>, dag@CONTROL.LTH.SE (Dag Bruck) writes:
|> Environment: InterViews 2.6 with patches, Sun-4, SunOS 4.1.1, Cfront 2.1.
|> 
|> I create bitmap objects using the constructor
|> 
|> 	Bitmap(const char* filename);
|> 
|> However, if the given filename doesn't refer to a valid bitmap file,
|> I get some strange X protocol error later on.
|> 
|> QUESTION: How do I check that the created Bitmap object really refers
|> to a valid bitmap?

This is a bug.  3.0 no longer has that constructor, but instead has a static member
function "open" that returns a Bitmap* if the file is found or nil otherwise.