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

Announcement

Collapse

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

Javascript & Build 8000-5628

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Javascript & Build 8000-5628

    Hi All

    I installed Build 8000-5628 on the 2nd January and I am having problems that it won't execute javascript that has been working for the last 5 years

    Two examples are below, I have recalculated all the controls on my UX taken sanitize off with no success I have loaded backups of the UX but still no joy.

    Does anybody have any ideas of what I might try?

    Andy

    Code:
    {dialog.Object}.setValue('Pay_Type','Cash');
    
    var _ok = function() {
    {dialog.object}.runAction('PayOnLine');
    };
    
    var _err = function() {
    THE FUNCTION IS ALWAYS ENDING UP HERE AND ALERTING THAT IT DID NOT RESPOND
    alert('server did not respond');
    {dialog.object}.runAction('PayOffLine');
    };
    
    //wait up to 2000 milliseconds before calling either the _ok or _err callback function
    {dialog.object}.serverIsAvailable(2000,_ok,_err);

    Code:
     data = lObj._rData;
    var html = '',
    sttl = 0;
    for (var i = 0; i < data.length; i++) {
    html += '<LEFT><SMALL> ' + data[i].PRICE +' ' + data[i].NAME + '<br>'
    sttl += +data[i].PRICE;
    };
    
    
    
    var _d = {"name": vStore,"Add1": vAdd1,"Add2": vAdd2,"City": vCity,"Pcode": vPostCode,"vat": vVAT,"paid": vTen,"Change": vChange,"Subtotal": vSub};
    
    var _h = '<center><BIG>' + _d.name + '<br>';
    _h += '<center><Small>' + _d.Add1 + '<br>';
    _h += '<center><Small>' + _d.Add2 + '<br>';
    _h += '<center><Small>' + _d.City + '<br>';
    _h += '<center><Small>' + _d.Pcode + '<br><br>';
    
    //footer part
    var _f = '<BOLD><SMALL><LEFT>Sub Total VAT Total<br>';
    _f += '<BOLD><SMALL><LEFT>' + _d.Subtotal + ' ' + _d.vat + ' ' + vTot + '<br>';
    _f += 'Paid: ' + _d.paid + '<br>';
    _f += 'Discount:' + vS_Dic + '<br>';
    _f += 'Change: ' + vChange + '<br>';
    
     1
    var dt = new Date().toDateString();
    _f += 'Date: '+ dt + '<br>';
    _f += 'Order: '+ vOrder + '<br>';
    _f += 'Payment: '+ vpayment + '<br>';
    _f += 'Discount:'+ vApplyDisc + '<br>';
    //_f += 'Date: ' + dt.toFormat('dd/mm/yyyy') + '<br>';
    _f += '<LINE><SMALL><LEFT>Thank you for your purchase. Please retain for your records. ';
    _f += '<SMALL><LEFT> Please ensure you use the correct charging equipment for your device, mobile phone and tablet chargers can be dangerous.';
    _f += '<br><CUT><DRAWER>';
    
    //put it all together
    
    var vReceipt = '<LOGO2>' + _h + html +'<br>' + _f
    //alert(vReceipt);
    
    CODE FAILS HERE
    var sApp = startApp.set({
    "action":"ACTION_SEND",
    "type":"text/plain",
    "component": ["pe.diegoveloper.printing"],
    },
    {"EXTRA_TEXT":vReceipt /*dataToPrint*/
    });
    sApp.start(function() { /* success */
    console.log("PRINT OK");
    },
    function(error) { /* fail */
    alert(error);
    });


    #2
    Yep ... I've run into lots of these type of issues in build 8000.
    Another property you can try is turn off 'Temporarily lock event handlers' under the Advanced section.
    Also turn on 'Pre-render component at design time' if it isn't on already.
    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    Comment


      #3
      Have you stepped through your code in a debugger? What error is shown in the browser console?
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant​​

      Comment


        #4
        Hi Mike

        This is what I see

        Code:
        Uncaught ReferenceError: cordova is not defined
        at <anonymous>:1:1
        at Object.A5.loadJavascript (a5-79935624.js:3157)
        at SALES1_PageLayoutLivePreview.a5w?zaajldni=15338928&__livePreviewInBuilder=Yes:1041
        and
        VM397:88 Uncaught ReferenceError: startApp is not defined
        at tempfunction_190bec7c_23c6_416c_95ae_9a6929899dfa (eval at runAction (a5-7993562
        This is the code I have in the Javascript functions, which has worked for five years but now it has stopped, has something changed Javascript is just not my thing, It's for printing to a receipt printer (ESC/POS) the startApp is in the code below

        Code:
        cordova.define("com.lampa.startapp.startapp", function(require, exports, module) {
        /**
        com.lampa.startapp
        https://github.com/lampaa/com.lampa.startapp
        
        Phonegap plugin for check or launch other application in android device (iOS support).
        bug tracker: https://github.com/lampaa/com.lampa.startapp/issues
        */
        
        var exec = require('cordova/exec');
        
        module.exports = {
        /**
        * Set application params
        *
        * @param {Mixed} params params, view documentation https://github.com/lampaa/com.lampa.startapp
        * @param {Mixed} extra Extra fields
        * @param {Function} errorCallback The callback that is called when an error occurred when the program starts.
        *
        */
        
        set: function(params, extra) {
        var output = [params];
        
        if(extra != undefined) {
        output.push(extra);
        }
        else {
        output.push(null);
        }
        
        return {
        start: function(completeCallback, errorCallback) {
        completeCallback = completeCallback || function() {};
        errorCallback = errorCallback || function() {};
        
        exec(completeCallback, errorCallback, "startApp", "start", output);
        },
        check: function(completeCallback, errorCallback) {
        completeCallback = completeCallback || function() {};
        errorCallback = errorCallback || function() {};
        
        exec(completeCallback, errorCallback, "startApp", "check", output);
        },
        go: function(completeCallback, errorCallback) {
        completeCallback = completeCallback || function() {};
        errorCallback = errorCallback || function() {};
        
        exec(completeCallback, errorCallback, "startApp", "go", output);
        }
        }
        },
        /**
        * extra values
        */
        getExtras: function(completeCallback, errorCallback) {
        exec(completeCallback, errorCallback, "startApp", "getExtras", []);
        },
        getExtra: function(extraValue, completeCallback, errorCallback) {
        exec(completeCallback, errorCallback, "startApp", "getExtra", [extraValue]);
        },
        hasExtra: function(extraValue, completeCallback, errorCallback) {
        this.getExtra(extraValue, completeCallback, errorCallback);
        }
        }
        
        });

        Comment


          #5
          Any luck figuring this out?

          Comment


            #6
            if you cant use a nightly build go back pre 8000 to many issues in 8000
            Insanity: doing the same thing over and over again and expecting different results.
            Albert Einstein, (attributed)
            US (German-born) physicist (1879 - 1955)

            Comment


              #7
              Hi

              No I did not, I replaced the code with code just checking if I was online, I could not get the {dialog.object}.serverIsAvailable() to work consistently, I am also finding that on the AJAX callback setup I am having to uncheck the "Check Server is Available" if I don't it is timing out and reporting that my server is not online

              Comment


                #8
                I've been having trouble with serverIsAvailable as well. Several users throughout the country are getting the message even when in a good coverage area. I figured it was something with AT&T. The funny thing is we are running version 7564 for IIS and have not updated recently. I did install 7902 when it came out for testing but never moved to it.

                Comment


                  #9
                  Hi

                  I am in the UK so nothing to do with AT&T this side of the pond

                  Andy

                  Comment


                    #10
                    the server time is set to 2000 never going to happen change to 6000
                    Insanity: doing the same thing over and over again and expecting different results.
                    Albert Einstein, (attributed)
                    US (German-born) physicist (1879 - 1955)

                    Comment


                      #11
                      Originally posted by peteconway View Post
                      the server time is set to 2000 never going to happen change to 6000
                      Thanks Pete. I considered changing the default time. My concern is if the client is not getting a response in 2 seconds, then they must not have a very good connection to begin with. Do we want to attempt a sync over a poor connection? Previously we found that if a user has a list they are trying to sync and that list contains a picture, if the sync fails, then all the edits are not persisted to the file system (in our case an Android tablet). Then if the user closes the app, all their edits are lost. We were having users losing work at an alarming rate. Checking serverIsAvailable first seems to have almost completely fixed this problem for us.

                      Comment


                        #12
                        Andy, I am seeing with some users that serverIsAvailable constantly fails even when in a good coverage area. But putting their tablet in airplane mode and then taking it out solves the problem and serverIsAvailable works after that. It is like the tablet is stuck in some type of offline mode even though it is not offline (I am able to offer remote support to the tablet fine).

                        Has you are anyone else noticed this behavior? I've noticed this in the past. As a work around I used to run code {dialog.Object}._setSimulatedOnlineStatus('on') which would kind of trick the tablet into thinking it was online before trying a sync. This doesn't seem to be as effective anymore.

                        Comment

                        Working...
                        X