Closing a filepro application Window

[GCC Consulting]

> -----Original Message-----
> From: 
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com 
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
elestial.com] On Behalf Of Brian K. White
> Sent: Friday, September 28, 2007 11:37 AM
> To: filepro-list at lists.celestial.com
> Subject: Re: Closing a filepro application Window
> 
> 
> ----- Original Message -----
> From: "Kenneth Brody" <kenbrody at bestweb.net>
> To: "Don Coleman" <dcoleman at dgcreact.com>
> Cc: "'Filepro-List at Lists. Celestial. Com'" 
> <filepro-list at lists.celestial.com>
> Sent: Friday, September 28, 2007 9:45 AM
> Subject: RE: Closing a filepro application Window
> 
> 
> > Quoting Don Coleman (Thu, 27 Sep 2007 13:51:39 -0400):
> > [...]
> >>> filePro already uses a CtrlHandler for Ctrl-C and Ctrl-Break, so
> >>> it "shouldn't" be a major project to add the close event as well.
> > [...]
> >>
> >> Are you saying this is a modification that would have to 
> be made by 
> >> FPTECH
> >> and cannot be done by the developer (if I had a brain)?
> >
> > Yes, having filePro catch the close event and clean up, 
> like the *nix
> > version catches Ctrl-\, is something that would need to be done by
> > fPTech.  The solution proposed elsethread about disabling the close
> > button and menu choice, which could be done external to filePro
> > itself, apparently doesn't work in a console window.
> 
> As an admittedly kludgy work-around, might someone not write 
> their own 
> command shell which can run fp as a child and catch the same 
> events itself?
> 
> Like take the cmd.exe from ReactOS and hack in the handler, 
> and have your 
> desktop shortcut specify a command line that explicitly calls 
> the custom 
> cmd.exe with your normal fp batch file as the argument.

That would be interesting but requires that those using the windows version
have this program.

It make more sense for fp to write these into their code.  That way, fp
would be closed down properly as there would be routines for handling
closings
	1. from menu
	2. from *clerk
	3. from *report
	4. Index maintenance
	5. development programs

When one stops to think about it, having fptech set an option to disable the
[X] makes sense.  But it also makes sense to have them program the proper
response from fp programs when X is pressed.  

Richard Kreiss
GCC Consulting