Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

> ## Event log entry types and logging levels

> You enable event logging with any of three log entry types. Using three different entry types gives you greater control over what and when information is logged. Table 6–4 lists the events that are logged and the logging levels supported for each entry type.

> Table 6–4: Events logged by log entry type
> Log entry type | Information that is logged
> --- | ---
> `ProEvents.UI.Char` | Turns on logging of keystroke events for printable characters. Logged at level 2 (Basic) and higher.
> `ProEvents.UI.Command` | Turns on logging of keystroke events for nonprintable characters: TAB FN keys CTRL, SHIFT, ALT and their combinations PAGE DOWN, PAGE UP, HOME, END and Windows GUI events (WM events). Level 2 (Basic) logs nonprintable keystrokes and this subset of WM GUI events: `WM_SETFOCUS` `WM_KILLFOCUS` `WM_CLOSE` `WM_ENABLE` `WM_LBUTTONUP` `WM_LBUTTONDOWN` `WM_RBUTTONUP` `WM_RBUTTONDOWN` Developer Events U1-U10 Level 3 (Verbose) logs nonprintable keystrokes and all WM GUI events.
> `ProEvents.Other` | Turns on logging of COM, Async, and Socket events. Logged at level 2 (Basic) and higher. OpenEdge logs no `PUSH` and `POP` entries for COM events. At levels 2 and 3, OpenEdge logs COM events only when the application defines a trigger for the event, on the assumption that you are interested only in events for which you have written a trigger. At level 4 (Extended), OpenEdge logs all COM events.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095