View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005003||JEDI VCL||00 JVCL Components||public||2009-11-02 17:46||2009-11-02 19:01|
|Product Version||Daily / GIT|
|Target Version||Fixed in Version||3.39|
|Summary||0005003: JvAppEvent cause unforeseen bugs when using with JvDebugHandler.|
|Description||When you TJvAppEvents to your application where TJvDebugHandler was used, you get doubled exceptions.|
1) Exception dialog which is called from OnOtherDestination (in my sample). So for that this component was designed..
2) And then you get the default windows exception messagebox!
And all because of some "MultiCaster.DoException" from JvAppEvents.
|Additional Information||1) Run project, you will see the exception like it must be.|
2) Then uncomment the line in uses clause of Unit1.pas and run again - you will get the exception twice.
|Tags||No tags attached.|
JvAppEvent.zip (1,149 bytes)
I think problem is raised from fix for 0004290.
The solution can be simple. By changing this Application.OnExeption on when TJvAppEvents.OnException is assigned. But there must be a way to avoid calling this exception dialogs twice.
The problem is not JvAppEvents but the inclusion of the unit AppEvnts. If the VCL unit is in a uses clause, TJvDebugHandler will always call the original handler which shows the default exception dialog.
The mentioned "simple solution" doesn't work because AppEvnts create the TMultiCaster in its initialization block.
Fixed in SVN.
TJvDebugHandler now uses the AppEvnts unit itself.
|2009-11-02 17:46||ZENsan||New Issue|
|2009-11-02 17:46||ZENsan||File Added: JvAppEvent.zip|
|2009-11-02 17:53||ZENsan||Note Added: 0016849|
|2009-11-02 18:35||AHUser||Note Added: 0016850|
|2009-11-02 19:01||AHUser||Note Added: 0016851|
|2009-11-02 19:01||AHUser||Status||new => resolved|
|2009-11-02 19:01||AHUser||Fixed in Version||=> Daily / SVN|
|2009-11-02 19:01||AHUser||Resolution||open => fixed|
|2009-11-02 19:01||AHUser||Assigned To||=> AHUser|