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

Navigating a Parent List when a Child List Detail View is Dirty

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

    Navigating a Parent List when a Child List Detail View is Dirty

    I want to prevent navigation in a parent list control, it the child list's detail view is dirty.

    There are plenty of variables in setting this up, so I have attached a test UX.

    The lists are based on the video AA List Control - Cascading Lists. But I have added a Detail View to the child list.

    To use the test UX, the lists must be bound to the Northwind customer database. I am using MySQL.

    Here are some specifics:

    This is for a desktop web application.
    The child list has the Detail View sync policy set to "Perform client-to-server sync whenever user saves edits to a row in a list".
    I do not want to check the option in the child list Detail View tab to "Auto-commit detail view on row select".

    When the child list Detail View is dirty, and navigation is attempted in the parent list, it will fire the message from the child list "Warning - dirty Detail View record". This is good.

    But it will...
    a) Allow the navigation in the parent list to take place.
    b) Remove any edits that were made to the Detail View controls.

    In the parent list I then added code to test if the child list's Detail View is dirty. It true, it prevents navigation.

    Code:
    var listObj = {dialog.object}.getControl('list_Cities');
    if(listObj)  {
    	if(listObj.detailViewIsDirty() == true)  {
    	    return false;
    	}
    }
    This prevents the navigation, but it still remove any edits that were made to the Detail View controls. There is an Detail View event, modeChanged, that may be causing this. I added an alert to this event to test. It fires a lot, apparently even when the mode has not changed. The alert is commented out, so it must be enabled in the process of testing.

    I am using Build 4912-5055.

    What am I missing here?

    testCascadingLists.a5wcmp

    #2
    Re: Navigating a Parent List when a Child List Detail View is Dirty

    Disable the parent list if the child list is dirty. If they can't click on it, they can't navigate anywhere.

    Comment


      #3
      Re: Navigating a Parent List when a Child List Detail View is Dirty

      Disabling the parent list is a possible solution, but I am looking for something more subtle. I still want the warning message to fire.

      With the parent list disabled I don't see a way to fire an alert.

      I have been looking at the modeChanged event. It is supposed to fire when the mode changes, but it fires when clicking on either list, even though the mode has not changed.

      Comment


        #4
        Re: Navigating a Parent List when a Child List Detail View is Dirty

        I believe that standard practice would normally be to hide the parent list by the time you get around to editing a record in a child list.

        These were built for mobile use, so the parent list would often be on a different panel card, not on the same screen as the child list and it's details.

        I see what you are trying to do, but I'm just not sure the lists were built that way.

        If you allow them to click on the parent list, something is going to happen.

        Another possible solution:

        Do not use parent/child lists. The parent child relationship will ultimately override anything you are trying to do short of disabling the parent.

        Instead, turn that feature off and just have two individual lists. You can refresh and filter the child list yourself when you select an item in the parent. You already have the parent list's value as an argument that filters the child list - you are just controlling that filtering yourself now.

        Then you will have more control over when the child does and doesn't get refreshed.

        Comment


          #5
          Re: Navigating a Parent List when a Child List Detail View is Dirty

          The bug here is that when selecting a new row in the parent list when the child detail view is dirty, the detail view fields are reset. That should not happen.

          Selwyn has fixed it. It will be tomorrow's build.

          This is (one reason) why Alpha is so awesome. Less than four hours from bug report to being fixed! Probably would have been quicker but I sent the report way early in the morning.

          Comment

          Working...
          X