---
title: "Number Pad Unit Test"
slug: "number-pad-unit-test"
updated: 2022-10-12T20:04:03Z
published: 2022-10-12T20:04:04Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Number Pad Unit Test

## Number Pad Unit Test

*Examples and set up for the Number Pad widget*

The Number Pad Custom Widget allows you to increase the speed and improve the process of number entry for apps. For example, on touch screens where the keyboard is small, the widget can be used to improve the operator input. The unit test application helps you test out the widget and learn how to use it in your app.

## How It Works

The Number Pad Custom Widget allows you to input an Integer value and will return the value. There are events fired on each button click and "Enter" click.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Number%20Pad%20Unit%20Test_526008531.png)

## Setup

Set up options and recommended configurations:

**Props:** **Value** - output value from the widget after the enter button is pressed **Value Text** - output value in text format. They create ease of use in Table ID fields and retain any leading zeros.

**Events:** **Clicked** - Fires when any button is clicked. Event includes the current displayed value. If you want to have the displayed value availiable in your app, you can setup a Trigger on this event to write to a Variable. **Enter Clicked** - Fires when the enter button is clicked.

Here's an example of a trigger to write an event output to a variable: ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%2844%29.png)

**Widget**

**Widgets**are the elements that make up a specific **App Step.**Widgets can display information to users, collect user input, or trigger app logic.

*Common widgets include: Interactive Tables, Number inputs, Machine attribute widgets, and more.*

**Integer**

**Integers**are a Tulip Datatype. Integers can have any whole number.

*ex. -5, 15, 47, 155. **NOT** 15.2, -12.73*

**Tulip Tables**

**Tulip Tables** are a global location to store your production data. **Tables** are made up of **Records** (rows). A single can be accessed from multiple apps or stations at the same time. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Tulip%20Tables%20Overview%20-%20Feature%20Overview(1).gif)

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.

**Variable**

**Variables**are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.