🚀 go-pugleaf

Mike Collins wrote:

>Hi all, posted a few days ago about a console application i was writing, 
>specifically processing messages within.

I don't use a message loop in my console app, but this is how I handle the handler.


static void EmergencyShutdown(void)	/*  we are getting out of here the hard way  */
{	throw_away_keys();		/*  toss any queued keys  */	
#if	UDP
	if( UDPRunning )
		KillUDP();	/* up to 5 sec delay */
#endif
	AppCanceled = TRUE;

	UnwindLockQue();
	UnwindFileQue();
	UnwindManagedIndexes();

	/*  remove myself from the handler queue  */
	SetConsoleCtrlHandler( &CtrlHandler, FALSE);
}

static BOOL _stdcall CtrlHandler(DWORD fdwCtrlType)
{
    switch (fdwCtrlType)
    { 
	/* Handle the CTRL+C signal. */ 
	case CTRL_C_EVENT: 
		push_key(CtrlC);	/*  pass Ctrl-C to app  */
		return TRUE;
 
	/* CTRL+CLOSE: confirm that the user wants to exit. */
/*	Ctrl_Close _needs_ to return False because I don't want a dialog poping up.
	Other events return True because I handled them this time,
	 and disabled myself so subsequent events will be false.
*/
	case CTRL_CLOSE_EVENT:
	case CTRL_BREAK_EVENT:
		EmergencyShutdown();
		return FALSE;	// next handler terminates me
 
	/* Pass other signals to the next handler. */ 
	/* Next handler will pop a terminate dialog */
	case CTRL_LOGOFF_EVENT:
	case CTRL_SHUTDOWN_EVENT: 
		EmergencyShutdown();
		return TRUE;
	default:
		return FALSE;
    }; 
}

Then, all sub-threads, such as a watchdog timer, check AppCanceled.
The application itself isn't going to run after I return.

>  The code seems to work but when i hit 
>Ctrl+Break the console application does not terminate.

Thanks, mine wasn't working either, then I switched it to FALSE
(see above), it terminated fine.

It could well be that because you don't discriminate in the handler,
that you enter an endless PostQuit-Close loop.
I would suggest turning off the handler within the handler.
That would eliminate the looping.