1. Definition of Input Measures

In HCI and interactive systems, input measures define how the system receives, interprets, and responds to user actions. They determine the granularity and timing of input processing.

There are three common input measures:

2. Event-Based Input

Definition:

• Event-based input refers to discrete input actions that trigger immediate notifications to the system.
• Each user action (like a keystroke, mouse click, or touchscreen tap) generates an event.

Characteristics:

• Input is asynchronous: the system responds when an event occurs.
• Events are independent and often queued for processing.
• Common in graphical user interfaces.

Examples:

• Pressing a key → generates a keypress event
• Clicking a mouse button → generates a mouse click event
• Dragging an object → generates a sequence of events (mouse down, motion, mouse up)

Advantages:

• Efficient for sporadic user actions
• System responds only when necessary

3. Sample-Based Input

Definition:

• Sample-based input refers to continuous monitoring of input devices at regular intervals (samples).
• The system records the state of the input device at each sampling point.

Characteristics:

• Input is periodic, not event-driven
• Often used for continuous control devices like joysticks, graphics tablets, or motion sensors
• Sampling rate is critical: too slow → lag; too fast → unnecessary processing

Examples:

• Joystick position sampled 60 times per second
• Touchscreen detecting continuous finger motion
• Motion capture systems recording positions of sensors

Advantages:

• Suitable for continuous, smooth interaction
• Enables tracking of position, velocity, or pressure over time

4. Request-Based Input

Definition:

• Request-based input occurs when the system explicitly asks for input before proceeding.
• The system is in a waiting state, and user input is required to continue execution.

Characteristics:

• Input is synchronous with program execution
• Typical in command-line interfaces or certain forms and dialogues

Examples:

• A program prompts: “Enter your username:” → waits for user input
• Dialog boxes in GUI: “Do you want to save changes?”
• Menu selection where the system pauses until a choice is made

Advantages:

• Simple to implement
• Ensures input is received before system moves forward

5. Comparison of Input Measures

6. Summary

• Event input: Best for discrete, sporadic actions (clicks, keystrokes)
• Sample input: Best for continuous, high-resolution input (motion tracking, drawing)
• Request input: Best for controlled, synchronous input where the system waits for the user

These measures are fundamental in designing responsive and user-friendly interactive systems in HCI.