Subj : OpenDoors (BBS door development)
To   : All
From : Nightfox
Date : Thu Sep 17 2009 05:14 pm

Today I started experimenting with OpenDoors to write a BBS door program.  I
was using MS Visual Studio 2008, compiling a Win32 executable.

I was running into a couple issues..  For one, using od_printf() didn't output
anything to my terminal program on the remote side (I only saw the text locally
on my BBS machine).

Second, since I'm compiling for Windows, OpenDoors seems to expect/assume that
I'm writing a program with a WinMain function (rather than the standard main
function), as in:
int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR
lpszCmdLine, int nCmdShow)
For example, I want to use the od_parse_cmd_line() function.  There are 2
versions of that function, one which requires the use of a WinMain function
(for its lpszCmdLine), and another for use with DOS, which uses argc and argv. 
The version of that function that uses argc and argv wasn't recognized by the
compiler, so I startd writing my door as a Windows app, using a WinMain
function.

Because I was writing it as a Windows app, the app has a GUI, probably provided
by OpenDoors.  I was closing the door application on my BBS machine, but after
checking the task manager, I noticed that the door program was still running. 
I've seen this before with GUI apps, and usually it means that the GUI window
wa closed but the application hasn't exited yet.  This even happened with one
of the example doors provided for OpenDoors.  So what I'd like to know is, if
you're writing a Win32 door with OpenDoors, how do you ensure that the program
exits when its GUI window on the BBS machine is closed?

Has anyone run into these issues and solved them?

Eric

---
 þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

.