🚀 go-pugleaf

In article 20033@athena.mit.edu, yev_g@athena.mit.edu (Yevgeny Gurevich) writes:
>In article <1992Sep13.065343.25286@silogic.uucp> markd@silogic.uucp (Mark C. DiVecchio (K3FWT)) writes:
>>
>
>>When I run it by double clicking on the program name using the
>>File Manager, it won't put up the dialog box on exiting but rather
>>gets a Error 5.
>>
>
>You're right in thinking that your application needs to access
>BWCC.DLL. >yev_g@athena.mit.edu
>500 Memorial Drive, Cambridge, MA.  [ Yevgeny Gurevich ]

While it is possible that not having BWCC.DLL loaded is the source
of the problem, my experience has been that apps that have the BWCC 
problem manifest the symptom of simply never appearing on the screen,
like you double-click on them and nothing happens.

BTW, to load BWCC.DLL, all you do is make sure to link app w/ BWCC.LIB,
#include <bwcc.h> and call BWCCGetVersion() at the beginning of the
program (myTApplication::InitMainWindow() is the standard place)

but I was going to say that the error -5 usually happens when the
program tries to load a resource (such as a dialog box) and fails. This
could happen if you had created an external binary resource file for
the dialog box. In this case, if you did not start up the program in
the directory where this resource was located, (quite posssible that
FileManager does not do this) then a load of the resource would fail,
resulting in the error -5. Hope it helps.

---
---------------------------------------------------------
                                       cyberspace
momma, don't let yer children grow up to be ^ cowboys ...
---------------------------------------------------------