Details | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 1 | daniel-mar | 1 | |
| 2 | Notes on debugging your application using TZipMaster or TZipBuilder: |
||
| 3 | |||
| 4 | |||
| 5 | If there's anything wrong with your event handler procedures, |
||
| 6 | you may get an error message from Windows saying something |
||
| 7 | is wrong with one of the DLLs. |
||
| 8 | |||
| 9 | |||
| 10 | This is because the DLLs become the "active program" when they |
||
| 11 | are busy, and your event handlers are "slave" functions/procedures. |
||
| 12 | Any serious errors in your event handlers will be reported as |
||
| 13 | problems with the "active program", which is the DLL. |
||
| 14 | |||
| 15 | |||
| 16 | I made a special ability for you to "Trace" thru the DLLs! This |
||
| 17 | does not require any knowledge of the C language, and you don't |
||
| 18 | need the source code. The DLL's have a built-in ability to report |
||
| 19 | their status at various key points and you can see these status |
||
| 20 | messages by hooking the OnMessage event. Just set the Trace property |
||
| 21 | to True, hook the OnMessage event handler, and you can see what is |
||
| 22 | going on inside the DLLs! |
||
| 23 | |||
| 24 | Eric Engler |
||
| 25 | englere@abraxis.com |