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

Working Preview vs Android

  • Filter
  • Time
  • Show
Clear All
new posts

  • Working Preview vs Android

    I'm getting variations between the Woking Preview and the live running on an Android tablet

    My two major problems are
    (1) I have client side formatting on a text field, which is a mask of 00:00; works fine in working preview - the android device behaves like its not there
    (2) I have some JavaScript that returns a message made up of several strings concatenated together separated by \r works fine in working preview and shows as separate lines - the android displays it as one long line

    Anyone any thoughts?

  • #2
    Re: Working Preview vs Andoid

    You don't say what Alpha build you're using or if it's a web app or a PhoneGap Build app... or how you're displaying the message.

    I don't see an issue with the client-side formatting. I have a Textbox Control with a client-side formatting mask of 00:00 and a default value of 1234. The display is 12:34. I then use a .setValue() on the Textbox of '4444' and 44:44.

    For the "message"... what are you using to display the message? If an "alert()", instead of \r (which is Carriage Return) use \n (Line Feed). If the message is being displayed by something that thinks it's html then use <br>.

    A simple UX showing your issues would help.


    • #3
      Re: Working Preview vs Andoid

      Alpha Build 4119 using Phone Gap cli-6.4.0

      You were dead right about the message \n sorted it right out! Thanks

      For the formatting I have a simple character field; I have ticked "Client side formatting"; the "Format Type" is set to "Mask" and the "Format definition" is set to 00:00. This works exactly as it should do in Working Preview but on the Android device it behaves like none of the above is set i.e. you can type the word "HELLO" into the box


      • #4
        Re: Working Preview vs Andoid

        I've forgotten about this so many times... but Selwyn never does... and he reminded me that this is an issue with the Android WebView and Chrome under Android. It's been around for years but Google can't or won't fix it. This has nothing to do with Alpha.

        However, some Javascript might be able to take care of this specific issue for you. Given that you're working with a Mask of 00:00, this code works on the data input and re-formats it if needed... allowing only numbers to be input. I've tested it quite a bit so let me know if you run into a case that does not give the desired results.

        In your UX onRenderComplete event...

        {dialog.Object}.__prevOrigVal = '';
        In your Javscript functions...

        function captureKey(){
        		var origVal = {dialog.Object}.getValue('formatTest');
        		var maskVal = origVal;
        		currVal = origVal.replace(':','');
        			maskVal = origVal.substr(0,origVal.length-1);
        				case (origVal.length == 2):
        						maskVal = origVal;
        						maskVal = origVal + ":";
        				case (origVal.length == 3):
        						maskVal = origVal;
        						maskVal = origVal.substr(0,2) + ':' + origVal.substr(2,1);
        				case (origVal.length > 4):
        					maskVal = origVal.substr(0,5);
        		{dialog.Object}.__prevOrigVal = maskVal;
        And in your Textbox control onKeyUp event...



        • #5
          Re: Working Preview vs Andoid

          Thank you very much for that and it works very well.