Video – Using QwikTouchPro with an Electronic Scale

Introduced in v0.1.40 (Available upon request only)

Part 1 (5:58)
Creating a Datasource for the Scale

Displaying the weight from the scale in real-time

String Formatting

There are several places in the QwikTouchPro Editor where you can provide an optional string format.

We use string formatting when we are retuning a value from a Datasource or another control and we want to change the way it is displayed.

String formatting is how we convert 7.2 to $7.20, or “11/8/2011” to “November 8, 2011” for e.g.

As of this writing, you can apply a String Format in the following places –

• Data Binding (Data Tab, Data Binding Group)
• Source Control Builder (Anywhere you see this icon -)
• DataGrid Columns (Data Controls Tab, Datagrid Group, Configure)

One of the more common uses for string formatting will probably be to format prices from Keystrokes as dollar amounts.  When you create a Customer Display or a collection of inventory items they are displayed the way they come out of the Keystroke Data port or Export.txt files.

This often means 0, 1, 1.5, or 17.32, when what we really want to see is $0.00, $1.00, $1.50, or $17.32.

To accomplish this we can apply a String Format to the price to convert it from a number to a dollar amount (currency).

The string format for currency is –

                {0:c}

Here is an example of a currency string format being applied to the Amount Due field from the Keystroke Dataport –

Here is a great link to some string formats –

http://blog.stevex.net/string-formatting-in-csharp/

(Scroll down to where the string format examples begin)

And here is a link of some common examples –

http://blog.stevex.net/2007/09/string-formatting-faq/

You can also use string formatting to specify the image for a Keystroke Inventory Item.

We know that the Images in Keystrokes are named I[StockNumber].jpg.

If we know the Stock Number of an item we can build the path to its image with string formatting.

{0} is a token that represents the string we are formatting (the Stock number of the selected item for example).

To get the full path of the image we would format the string as –

C:\Keystrok\Tutor\PHOTOS\I{0}.jpg

At runtime, QwikTouchPro will replace the {0} with the stock number of the selected item.

Video - Creating a Keystroke Customer Display

This 15 minute video walks through creating a simple Keystrok customer display in QwikTouchPro.

A customer display is a template that displays real-time sales information as it is entered into Keystrokes.  Customer Displays can also display advertising and might be run on a second monitor or other remote display where the customer can see them.

The steps to create a Customer Display are detailed in the Video, but they are –

o   Enable the Dataport in KeystrokePOS

o   Create a Datasource in the QwikTouchPro Editor

§  A configuration file that points to the Keystroke Dataport          

o   Add (and Bind) Text controls for the invoice data

o   Add (and configure) a Datagrid to display the line items

The Customer Display created in this video very basic.  Your actual customer display can contain media (Images, Videos, Flash Videos, Web Pages) as well as dynamic advertising and advanced macros.

Your customer display could, for example, display different information depending on the current sales invoice -

·         Show different customer displays to different customers

o   Walk-ins can see a different Customer Display than your regular customers

o   Customers could be flagged in your Keystroke Database to allow for more customized displays

§  E.g.  Mark a Customer a “GoldClub” member and show them a fancy golden template with specific advertising

·         Display a message (or Template, or Sub-Template) depending on the Invoice Total

·         Display custom advertising/info about the department of the last item added to the sale

·         Display an image of the last inventory item added to the sale

·         Much More...

Datagrid Options

I didn’t talk about these in the video so here is a quick overview –

Scroll to Last Row on Update – This option scrolls the Datagrid to the bottom when an item is added.  With a customer display you will probably want to show the bottom of the list of Line Items and not the top, so that the customer will always see the last item added.

Select Last Row on Update – This option selects the last row (but does not scroll to it) of the Datagrid when an item is added.   You can use this to highlight the most recent item, and also to create macros.

Play Click Sound on Selection – This option will play the default click sound when an item on the Datagrid is selected (by touching it, or via the “Select Last Row on Update” option).

You might disable this option when using the “Select Last Row on Update” option so don’t hear the click sound as items are added to the sale.

The default click sound can be changed by right clicking the QwikTouchPro icon in the system right and choosing properties (requires that QwikTouchPro be running).


Here are a few sample Customer Displays from an earlier Blog Post.

Video - Modifying the Standard16x11 Template

This 9 minute video demonstrates adding some keys to the Standard Template. 

The new keys will ring up a few promotional items in Keystrokes.

 

The latest Standard16x11 templates can be downloaded here

http://hercemer.dyndns.org/QTP/Templates/Standard16x11.zip

Using KeystrokePOS with QwikTouchPro

This post will describe how to configure QwikTouchPro to work with KeystrokePOS.

The first step is to create a Program File that describes KeystrokePOS to QwikTouchPro.

See this post for information on creating programs http://qwiktouchpro.blogspot.com/2011/11/introduction-to-programs.html

Here is a sample Keystroke Configuration

Executable: Browse to Keystrok.exe

Switches: Optional, you can use an INI file instead

KSTemp File: This is only required if you want QwikTouchPro to be able to move and size your Keystroke window.

This file will be called DPx.tmp (where x is your register number) and it will be created in the current Keystroke Data Folder (c:\keystroke\Tutor in this example).

Use Existing Process From Task Manager:  We use this option to tell QwikTouchPro to try and find a running copy of Keystroke instead of opening a new one.

Process Name:  Keystrok

The Process Name is how QwikTouchPro finds the running copy of Keystroke, it looks at all running programs for one named “Keystrok”.

Show Window:  Run Keystroke in a window that the user can see and interact with.

Start/Restart on Activation:  This has no effect on Keystroke

Start Maximized:  We could start Keystroke full screen, but we will be using a “Move Program” Macro to precisely move and size it instead.

Wait for Exit:   This has not effect on Keystroke.

Once you have created and saved your Keystrok.qtp configuration file, you can use it in macros.

Making Changes

If you change the way Keystroke is configured you will need to edit and update the Keystrok.qtp file (though the Edit Program Button on the Data Tab).

e.g., if we wanted to change our sample configuration from the Tutor Folder to the Data Folder we would make the following changes:

The Switches need to be updated from /D TUTOR to /D DATA

The KSTemp file needs to be updated to c:\Keystroke\Data\DP1.TMP

Example Macros

Open Keystroke when the Template Loads

This macro will open a copy of Keystroke when this template loads.  Remember we can call “Open Program” as often as we would like without worrying about opening multiple copies of Keystroke.

Close Keystroke when the users touches a Button

This macro will close Keystroke when the user touches a Button

 

Move Keystroke when the users touches a Button

This macro will move and size Keystroke when the user touches the button.  This macro requires a Program Window control be added to your template.  The Program Window control is how QwikTouchPro knows where and how to display Keystroke.

Trouble Shooting

Some common problems and possible solutions.

Problem:  A new copy of Keystroke opens every time the “Open Program – Keystroke” Macro is performed.

Solution:  Confirm the Process Name in the Program Setup is correct (should be Keystrok) and that “Use existing process from Task Manager” is checked.

Problem:  Error finding Keystroke Temp File

Solution:  Confirm that you have selected the correct DPx.TMP file.  You may have to examine your Keystroke [Data] folder (Data, Tutor etc…) to make sure there is a DPx.TMP file being created and that you are selecting the correct file.

Problem:  The “Move Program – Keystroke” Macro doesn’t do anything.

Solution:  Confirm that you have selected the correct DPx.TMP file.  You may have to examine your Keystroke [Data] folder to make sure there is a DPx.TMP file being created and that you are selecting the correct file.

Problem:  Keystrokes is open, but “Send Text” Macros are not working.

Solution:  QwikTouchPro sends commands to the Active Program.  Even though Keystroke may be visible, it may not be active (does not have the focus).

To correct this, you may have to add an additional Macro to “Move Program – Keystroke”.  The “Move Program” Macro will give Keystroke POS the focus as well as moving and sizing it.

Introduction to Programs

QwikTouchPro Program Files (*.qtp) are configuration files that tell QwikTouchPro how to work with other applications like Keystroke, Notepad or Microsoft Word.

Program Files are stored in your QwikTouchPro Programs folder (default is c:\program files\QwikTouchPro\Programs) and can be reused and shared.

These Program Files can be referenced by any and all of your templates, and can be quickly updated.  If your Keystroke directory changes for example, you can simply edit the Keystroke.qtp file and any templates using that file will use the new configuration.

You create and manage program files from the QwikTouchPro Editor by selecting the Data Tab, Programs Group, and New or Edit Program.

The New Program Dialog

Executable:  Browse to the Application you want to work with

                Example: c:\Keystroke\Keystrok.exe    

Path:  Auto Filled when you select the Executable

Switches (optional):  Any command line switches your application requires.

KS Temp File (optional):  This is a small text file that Keystroke POS generates and is required for QwikTouchPro to be able to move and size it.  This field is only required for Keystroke and can be ignored for all other applications.

Options

Use Existing Process from Task Manager:  This option tells QwikTouchPro to look for a running instance of a program instead of opening a new one. 

When QwikTouchPro tries to open your application, it will first look through your currently running applications.  If it finds a copy of your application is already running, QwikTouchPro will use that instance instead of opening a new one. 

This is to allow you to call “Open Program” Macros without having to worry about opening the application more than 1 time.

For e.g., you could call “Open Keystroke” as often as you like, and if Keystroke is already running, nothing will happen.  This is an easy way to make sure programs are open when you need them – when in doubt you can call the Open Program Macro with no adverse effects.

Process Name:  This is the name of the application as it appears in the Task Manager without the extension - e.g. Notepad, Keystok.

The Process Name field is required by the “Use Existing Process” option.

Show Window:  Opens the Application in a visible window so the user can see it. 

There may be applications you want to run in the background that the user should not see (like kicking off an export, or restarting a service).

Start/Restart on Activation:  This option will automatically try to start or restart and application if you call the “Activate Program” Macro.

This option is to make it easy to ensure that your application is open and active when you go to use it.

One Macro - “Activate Program” will open the Application and bring it to the forefront, saving you the extra step of adding a second “Open Program” Macro.

(this setting has no effect on KeystrokePOS)

Start Maximized:  Start the Application Maximized. If you do not select this option, QwikTouchPro will open the Application at whatever its default or last size was.

Wait for Exit:  This option will cause QwikTouchPro to wait for the Application to exit before continuing on.

You might use this when running KSExport.exe to make sure the export finishes before allowing the user to continue on.

When you click Create you will be prompted to save your Program File.  I recommend naming the file so that you can easily tell the application it will be used for.

e.g.  Keystroke.qtp, Notepad.qtp, KSExport.qtp