In D5 there is a new non-visual component under the Additional tab called
TApplicationEvents. This allows you to hook into the global Application var
events through the TApplicationEvents events oldly enough. I was checking
out the ability to easily add exception handlers for indvidual forms and
when I finished with it I deleted the component from the form. But it still
left the reference to AppEvents.pas in the forms uses clause. This is where
the problem occured.
For some unknown reason by just having that pas referenced, but not being
used directly by me, it was adding its own eventhandler by hooking into
Application.OnException. It was then doing nothing when an exception was
raised by my app! It was not even showing the exception message to me! The
only way I could find out about any exceptions (including asserts as they
are exceptions) was to be running under the IDE and seeing them occur. It
was effectivly supressing the exceptions. The way to solve this is to just
simply remove the AppEvents.pas reference in the uses clause.
Anyway I thought that I would warn you all so you don't end up wasting a
large amount of time with it like I have.
Also, don't ALT+F12 a TFrame, do some editing like change component types
then ALT+F12 again because it frags part of the projects settings, including
all compiler, linker and path ones!
I think that the addage of 'New features in Delphi won't be stable till the
next version or big patches comes out' still applies, even to D5. <sigh>
Enjoy christmas and the new year!
Nahum Wild
ESDAO Product Manager
Realism
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
