> <IMHO>
> I might question why an application should 'lock up' without
> throwing an exception since it then implies an infinite loop or
> processing intensive loop failing to give user feedback during
processing.
> <IMHO>
Sounds like a very good UI idea to always keep the user informed during
processing or at least have plenty of application.processmessages but I
have been working a fair bit with non-UI server applications that handle
serial comms - you tend to not want to do too much mucking around when
doing high speed comms <g>.
As for infinite loops - hands up everybody who has done dumb things
like:
while (not table1.eof) do
begin
listbox.add(table1.Name.AsString);
end;
> Even so, perhaps it is possible to supply a message handler for the
> 'close application' sent by windows pior to forcing a shutdown.
Yep but we now getting to the stage of having startup code check, and
special handlers on shut-down, exception handling and close application.
Why not just drop a check_all_windows_on_startup procedure/component on
the app (or better still have it built into your standard application
framework).
All the code is then in one place, no worries and always works.
Grant Black
Software Developer
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
