Velocity powered by Wavelink
META tags are included at the top of a web page within the <head> and </head> tags. They are evaluated in the order they appear in the web page (from top to bottom). Velocity ignores tags it does not recognize.
Each META tag has the following format:
The following META tags are supported by the Velocity Client.
The OnKey and OnKey0x META tags describe an action that will occur if a particular key is pressed. The key values evaluated are the same key values used by the Velocity Console. The OnKey0x format requires a unicode value and the OnKey format requires a decimal format. The key value is case sensitive.
OnKey0x32 respond when the user presses 2.
OnKey97 respond to both the upper and lowercase A.
The OnAllKeys tag will perform the specified action each time any key is pressed. The action type can include one argument, which is the string representing the decimal value of the key.
An example of this tag in use is provided below.
<Title>META Tag Onloaded Example</Title>
<p>This is a sample test page.</p>
In this example, the function helloWorld() is called to display an alert on the device when the screen is fully loaded.
This section includes tags that enable or disable the scanner or specific symbologies.
If the action name is
Scanner and the action type is
Enable , the scanner will be enabled when the page is first loaded. If the action type is
Disable , the scanner will be disabled when the page is first loaded.
The additional scanner action types supported by the Velocity Client include:
Enable and disable different scanner symbologies by using the symbology as the action name, and
Disabled as the action type. The symbologies supported by the Velocity Browser are:
In addition to the listed symbologies, the value ALL_DECODERS can be used to enable or disable all the symbologies.
For example, to enable only UPCA use the META tags in this order:
<meta http-equiv="ALL_DECODERS" content="Disabled">
<meta http-equiv="UPCA" content="Enabled">
You can execute scripts from web pages using the wls tag, followed by the script name or API, with or without parameters.
•Executing from the meta tag: This example launches a script called WebAuto when the web page first loads.
<title>TE70 Test1 - Launch Telnet Scripts</title>
<meta http-equiv="OnStartup" content="wls:WebAuto">
•Executing from an href: This example launches a script called WebClick when a user clicks the hyperlink "here" on the web page.
Click <a href="wls:WebClick">here</a> to launch the "WebClick" script.
var request = "wls:dnwebdemo";
•Executing with an API: This works almost exactly like calling a Wavelink script with parameters above. Instead, replace the script name with the API and enter the parameters associated.
Click <a href="wls:Device.beep(200,500,50)">here</a> to launch the "Device.beep" API.
Was this article useful?
The topic was:
Not what I expected
Copyright © 2017, Ivanti. All rights reserved.