Knowledge Base

Coding Scheme

Only uLog events that have been logged are added to the coding scheme when a log file is imported in The Observer XT. Three different event types are added as mutually exclusive behavior groups:

• Mouse Events – With the mouse clicks, double-clicks, mouse wheel turns and mouse drags as point events.
• Keyboard Events – With the characters and keys typed as point events. This group also contains the behavior String, which combines the key presses separated by pressing a special key, like the space bar, enter key, or backspace key, to words.
• Other Events – With events like starting and stopping applications, activation of windows and browsing behavior.

The Coding Scheme also contains a number of modifier groups:

• ControlType – Linked to the behaviors Mouse click, Mouse doubleclick and Mousewheel turn. This modifier specifies, for example, where a mouse click took place. The individual modifiers are:
  • listitem
  • edit
  • tabitem
  • combobox
  • pane
  • window
  • button
  • slider
  • group
  • list
  • headeritem
  • dataitem
  • document
• KeyboardCharacter – That contains the logged characters.
• KeyboardSpecialKey – That contains the special keys:
  • Backspace
  • Arrow
  • Return
  • Space
  • Alt key with Numpad keys
• KeyboardKeyCombination – That contains the key combinations like Ctrl + S, or Ctrl + A.
• MouseButton – Which button is used, left, right, or middle.
• ApplicationName – Which application is opened, or closed.
• MouseX – The X coordinate in pixels of the mouse event starting from the left side of your screen.
• MouseY – The Y coordinate in pixels of the mouse event starting from the upper side of your screen.

The name of applications and web pages in which events took place and typed text are imported as comments in the Event Log.

Events in Event Log

The figure below shows an example of how the events are shown in the Event Log. The test participant used the Windows + D key combination to switch to their desktop, started Google Chrome and typed my.noldus.com to access their MyNoldus account.

Technical Support

Noldus Help Desk

If you have any problems, questions, remarks or comments, please let us know. We offer 24 hour support via help desks in different time zones. From the Help menu choose Noldus Online and subsequently Contact Help Desk. This brings you to the MyNoldus portal on the Noldus website. Create a new account or log into your existing MyNoldus account. Under Get Support you will find the contact details of the help desk in your region, you can view the status of your current support cases or submit a new support case.

Before you contact the help desk, please have the following information available so our support staff can help you as quickly as possible.

• The version number of your copy of uLog (choose Help > About uLog).
• The name of the registered user of The Observer XT (choose Help > About The Observer XT > License Info).

Error Messages

All error messages are displayed in a Critical Message box. The error is displayed and, if possible, a solution. Whenever such an error occurs, a log file is created called uLog.log. The Technical Support Department may request this file when answering your support question. You can locate the file in:

C:\Users\Public\Public Documents\uLog\Log

Source: EthoVision XT 18 - THC - Trial and Hardware Control, Noldus Information Technology