Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Tablet Sample App: Custom Keypads

  • Filter
  • Time
  • Show
Clear All
new posts

    Tablet Sample App: Custom Keypads

    On desktop computers, they keyboard is a physical construct outside the software environment. You have no control over what keys the user may press. Consequentially, data validation is sometimes required in applications to ensure text entered for something like a phone number only contains numbers.

    In tablets and mobile devices, however, keyboards are emulated. This presents a unique opportunity. You can reduce the need for data validation and stop the user from entering bad data by providing customized keypads that only contain valid characters.

    In the sample tablet application, specialized keypads were built for capturing information for a car inspection. The Editors for the Odometer and VIN Number both use custom keypads. In this video, Dan Bricklin explains in detail how these keypads were built using a ViewBox and a bit of Javascript.

    Tablet Optimized Forms: Custom Keypads
    Presented by Dan Bricklin, Alpha Software CTO

    Video Link:

    Prerequisite Knowledge Base
    It's not necessary that you actually know what the sample application is for this video, but if you haven't seen it yet or want to download it, check out these awesome links:
    • Tablet Sample Application Overview: Presented by Dan Bricklin, Alpha Software CTO, this is an overview of the sample tablet application's features
    • Sample Tablet App: Get a copy of the sample tablet application and follow along!
    • ViewBoxes: Build a Star Rating: Custom keypads couldn't be built without ViewBoxes. Learn how to build a star rating control from scratch in this easy-to-follow step-by-step tutorial and discover how versatile the ViewBox can be.

    This video is pretty advanced. But don't that that deter you! If you have any questions or need help understanding what's going on, post your questions below so that we can help you out.
    Last edited by Sarah Mitchell; 09-11-2015, 05:26 PM. Reason: adding video library links
    Sarah Mitchell
    Director of Customer Success | [URL=""]Alpha Software Corporation[/URL]
    [B]Get in the know! [/B] Join us for our Weekly Webinars: [URL=""]TransForm Tuesday[/URL] and [URL=""]Wednesday's Alpha Anywhere Demo and Q&A[/URL]
    Connect with us: [URL=""]Instagram[/URL] | [URL=""]Twitter[/URL] | [URL=""]Facebook[/URL] | [URL=""]LinkedIn[/URL] | [URL=""]YouTube[/URL]

    Re: Tablet Sample App: Custom Keypads

    We need a keypad/keyboard template or control set that is a lot less abstracted than the ones used in this example, which are so integrated with the panel system in this example that they cannot be re-purposed for use in dis-similar projects, at least not with the ease that other examples of this type can.

    It seems that given the obvious nature of the interference caused by the native mobile device keyboards, a replacement keyboard/keypad component would have been the very FIRST component to be developed for "Tablet Optimized Forms" mobile apps. THE VERY FIRST!!!!!!!!

    Before our purchase of Alpha Anywhere, this was so obvious to me that I took it for granted that Alpha would have already taken care of this. Imagine my surprise that they did not, and my even greater surprise at this obfuscated, and abstract "example" that works perfectly well for its sample application, but is completely undecipherable for use in a project having a different navigation style.