Changes between Version 2 and Version 3 of Software/userlog
- Timestamp:
- 04/07/11 13:09:51 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Software/userlog
v2 v3 22 22 The target of the event is identified using the HWND of the GUI object that the event has been addressed to. 23 23 24 == = Architecture ===24 == Architecture == 25 25 26 26 The architecture of the logging mechanism is rather simple. It is a DLL written in C++. The interface provides currently only functions to start and stop the logging: … … 48 48 A ''log'' consists of several ''sessions'', i.e., program executions. Every session consists of the messages it recorded. A message consists of a ''type'' and of parameters. The of a message is describes by an integer that identifies the windows message that has been send, e.g., {{{WM_CREATE}}}, {{{WM_DESTROY}}} or {{{WM_LBUTTONCLICK}}}. The parameters are ''name'', ''value'' pairs, both stored as strings. Using the parameters, it is possible to store additional information to messages in a generic and flexible way. For example, in case a window is created additional information about the window, like its resource id. 49 49 50 == = How to use ===50 == How to use == 51 51 52 52 To enable the logging the {{{usagelog.dll}}} has to be loaded: … … 96 96 }}} 97 97 98 == = Further Features ===98 == Additional Features == 99 99 * Unicode logging 100 100 * encoding depends in compiler, UTF-16LE with Visual Studio 2008