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

Delete row in list control not working

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

    Delete row in list control not working

    I have 3 list controls (with detail view) in my mobile app and along with each are associated Save, New, Delete, Sync & Refresh buttons. I have the same issue with all 3 lists - which are otherwise working fine. I'd like to do away with the Sync and Refresh buttons to simplify the process.

    Before making the change below, when I selected a row and touch 'Delete' the row is marked for deletion. When I then touch 'Sync' the row is removed from the list and the SQL database table is updated accordingly - all good.

    What I want is for the 'Delete' button to do the delete and then sync the list. So, I modified the click event for the delete button to include the standard actions from both the delete and sync buttons as follows:

    Code:
    var lObj = {dialog.object}.getControl('DOWNTIMELIST');
    lObj.deleteRow();
    {dialog.object}.saveListEdits('DOWNTIMELIST',{rows: 'allRows'});
    The last line above is exactly as it is in the Sync click event.

    However, this doesn't work. I still have to touch 'Delete' followed by 'Sync' to complete the process. I've tried wrapping saveListEdits in a timeout in case there was some odd timing issue but this made no difference.

    This same concept is working fine for the save process.

    Code:
    var lObj = {dialog.object}.getControl('DOWNTIMELIST');
    lObj.updateListFromUXControls();
    {dialog.object}.saveListEdits('DOWNTIMELIST',{rows: 'allRows'});
    Does anyone have any ideas on why this isn't working for the delete?

    #2
    Re: Delete row in list control not working

    Originally posted by tirani View Post
    I have 3 list controls (with detail view) in my mobile app and along with each are associated Save, New, Delete, Sync & Refresh buttons. I have the same issue with all 3 lists - which are otherwise working fine. I'd like to do away with the Sync and Refresh buttons to simplify the process.

    Before making the change below, when I selected a row and touch 'Delete' the row is marked for deletion. When I then touch 'Sync' the row is removed from the list and the SQL database table is updated accordingly - all good.

    What I want is for the 'Delete' button to do the delete and then sync the list. So, I modified the click event for the delete button to include the standard actions from both the delete and sync buttons as follows:

    Code:
    var lObj = {dialog.object}.getControl('DOWNTIMELIST');
    lObj.deleteRow();
    {dialog.object}.saveListEdits('DOWNTIMELIST',{rows: 'allRows'});
    The last line above is exactly as it is in the Sync click event.

    However, this doesn't work. I still have to touch 'Delete' followed by 'Sync' to complete the process. I've tried wrapping saveListEdits in a timeout in case there was some odd timing issue but this made no difference.

    This same concept is working fine for the save process.

    Code:
    var lObj = {dialog.object}.getControl('DOWNTIMELIST');
    lObj.updateListFromUXControls();
    {dialog.object}.saveListEdits('DOWNTIMELIST',{rows: 'allRows'});
    Does anyone have any ideas on why this isn't working for the delete?
    Hi, in the detail view there is a sync policy option that may help you out. Basically it sets the client to server sync automatically when ever there is an Internet connection.

    Comment


      #3
      Re: Delete row in list control not working

      Thanks Ken

      I was aware of that setting but hadn't tried it. I've updated the app to use the client-to-server policy and it does indeed get around the issue.

      I'd still like to know why the code used above for the delete does not work though.

      Comment


        #4
        Re: Delete row in list control not working

        Originally posted by tirani View Post
        Thanks Ken

        I was aware of that setting but hadn't tried it. I've updated the app to use the client-to-server policy and it does indeed get around the issue.

        I'd still like to know why the code used above for the delete does not work though.
        Okay, here's my guess as I am swimming in the same waters as you as to how the sync process works under the covers with the myriad of configurable options. There is a help option for disconnected design in software and it's actually very good. Through a lot of trial and error I got my mobile app working but I don't understand all the bits and pieces.

        I think your issue has to do with the asynchronous nature of ajax callbacks and I would use the a5.executethisthenthat function to accomplish this as follows:

        When the user presses a button, I call the javascript function uploadSuccess.

        function a2() {
        var o = {dialog.object}.countRecordsToSynch('LIST5');
        alert ('Sending: ' + o.count + ' saved information to server, check each record for errors after upload');
        {dialog.object}.saveListEdits('LIST2',{rows: 'allRows'});
        }

        function a3() {
        //alert ('The upload is completed');
        var lObj = {dialog.object}.getControl('list5');
        var err=lObj.getAllErrors() <------------I'm experimenting with this
        alert(JSON.stringify(err));
        {dialog.object}.runAction('upload_message');
        }

        function uploadSuccess () {
        A5.executeThisThenThat(a2,a3);
        }

        Alternative you can use action javascript and check the option for synchronous execution.

        Comment


          #5
          Re: Delete row in list control not working

          OK, that sounds plausible. So, I turned off the sync policy for one of the lists and changed the click event for the delete button to the following.

          Code:
          function d1() {
          var lObj = {dialog.object}.getControl('BLOWUPLIST');
          lObj.deleteRow();
          }
          
          function d2() {
          {dialog.object}.saveListEdits('BLOWUPLIST',{rows: 'allRows'});
          }
          
          A5.executeThisThenThat(d1,d2);
          Unfortunately, this made no difference!

          I've also noticed that after deleting one row (which stays in the list flagged for deletion) if I then delete another row, the row flagged for deletion gets deleted and the second row remains flagged for deletion. This behaviour is the same if I use my original code.

          It does seem like a timing issue, as you've suggested, and I'm surprised the above changes made no difference.

          I see that there are numerous events relating to list operations, do you know if using these (such as afterDeleteRow) would be any better than just using the built in synchronisation policy?

          Comment


            #6
            Re: Delete row in list control not working

            Originally posted by tirani View Post
            OK, that sounds plausible. So, I turned off the sync policy for one of the lists and changed the click event for the delete button to the following.

            Code:
            function d1() {
            var lObj = {dialog.object}.getControl('BLOWUPLIST');
            lObj.deleteRow();
            }
            
            function d2() {
            {dialog.object}.saveListEdits('BLOWUPLIST',{rows: 'allRows'});
            }
            
            A5.executeThisThenThat(d1,d2);
            Unfortunately, this made no difference!

            I've also noticed that after deleting one row (which stays in the list flagged for deletion) if I then delete another row, the row flagged for deletion gets deleted and the second row remains flagged for deletion. This behaviour is the same if I use my original code.

            It does seem like a timing issue, as you've suggested, and I'm surprised the above changes made no difference.

            I see that there are numerous events relating to list operations, do you know if using these (such as afterDeleteRow) would be any better than just using the built in synchronisation policy?
            Hi,

            You shouldn't have to go down to those client side events and I can't wrap my head around why this isn't working for you. In my application I have a three tier layout utlimately in a phonegap application with changes only allowed at the lowest level. These means I have an add, insert, delete and sync button and the app works without an internet connection until it comes time to sync. While I wonder with you why this isn't working, in order to avoid driving yourself crazy, maybe set the sync policy in the interim. It's late here and I would like to help but time to go sleep; if I think of anything else I will post back. I'd like to know the answer also.

            Also tomorrow I'll see if I can put together a test case with some sample UXs that I have.

            Comment


              #7
              Re: Delete row in list control not working

              I've already put the sync policy back for now - got to get some user testing done. Thanks for your feedback.

              Comment

              Working...
              X