All the information collected by ImageGlue is written out into one of three log files. It is worth noting that the information contained within these files is different from the information written to the Event Log. If an error occurs or an unexpected condition is encountered then information is written to the Application Event Log. The log files are used for collecting statistics on normal transactions. Because there are a lot of transactions that could be logged we provide settings to allow you to reduce the volume down to only those that you are interested in.

The three log files are SaveAs.Log, Operation.Log and Canvas.Log. By default these are written out into a system-wide temporary directory so that they can easily be deleted if they get too large. They are written out in a tab delimited format with the first line containing the column headers.

SaveAs.Log contains information on every file saved using ImageGlue. This is essentially the same information as contained in the Operation log but selected in a different way. For example:

Version ID StartTime Duration(ms) Type CanvasID Path
1 3da75b3b Jun 01 10:31:41 2000 393 Save As: 71a04106 D:\DrawCanvas1.jpg
1 2ad76855 Jun 01 12:58:04 2000 529 Save As: 6c563110 D:\DrawCanvas1.jpg

Operation.log can contain the identity, type and duration of every operation performed on every canvas. However to restrict volume only operations that take longer than a minimum specified duration will actually be logged. For example:

Version ID StartTime Duration(ms) Type CanvasID Path
1 43aa2c32 Wed May 31 17:04:52 2000 389 Save As: 494f1fd2 D:\DrawCanvas1.jpg

Canvas.log can contain the size and duration of existence of every canvas created. Again, to restrict volume, only canvases that exist longer than a minimum specified duration will actually be logged. For example:

Version ID StartTime Duration(ms) Memory(KB)
1 71a04106 Jun 01 10:31:38 2000 46490 506
1 30650360 Jun 01 10:31:38 2000 50691 13
1 7cad6fee Jun 01 10:31:38 2000 50544 13