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

Stop the user from exiting without saving on a UX in an a5w page

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

    Stop the user from exiting without saving on a UX in an a5w page

    I have an issue where users are sometimes closing out of a UX when it is dirty. Unfortunately, there is no warning if you click the browser's refresh or close buttons.

    How can I keep the user from exiting an a5w page with a UX when it is dirty?

    If I put the UX in a tabbed UI, the tabbed UI has an options to warn the user, even if the browser were to be closed.

    How can I duplicate that same (or similar) feature outside of a tabbed UI?

    #2
    Re: Stop the user from exiting without saving on a UX in an a5w page

    This may not be technically correct, but unless you do something radical you probably won't be able to prevent it. If you add a container to the very top of your component 100% wide set the onmouseover to fire if the user is heading to the top of the screen while the UX is dirty.

    2018-08-17_2010.png
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


      #3
      Re: Stop the user from exiting without saving on a UX in an a5w page

      You may want to invoke the onbeforeunload event on the body tag. That fires just before a page is unloaded

      https://www.w3schools.com/tags/ev_onbeforeunload.asp

      https://www.w3schools.com/tags/tryit...onbeforeunload

      Comment


        #4
        Re: Stop the user from exiting without saving on a UX in an a5w page

        Its a good suggestion Jerry and thanks, but it's behaviour does vary from browser to browser - as crude as my suggestion is - it's in AA irrespective of browser, anyhow at least Larry has some options now - look forward to seeing you in Orlando.
        Note: In Firefox, only the default message will be displayed (not the custom message (if any)).
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #5
          Re: Stop the user from exiting without saving on a UX in an a5w page

          How does the tabbed UI do it? The option "Prompt when navigate away from page."

          It seems like there should be a way to use whatever that is doing in other places.

          Comment


            #6
            Re: Stop the user from exiting without saving on a UX in an a5w page

            To be honest this is one of the biggest issues for me so to resolve I work on the basis of (almost) all data entry/edit taking place in pop up windows where I can control the exit.
            Glen Schild



            My Blog

            Comment


              #7
              Re: Stop the user from exiting without saving on a UX in an a5w page

              I'm sure this can be done. Facebook, for example, prompts you when you have unsaved data if you try to close the browser or navigate away. Jerry's suggestion seems like the one to use. And like Pete said it may not be support on every browser. The method should check for some variable to see if the page/component is dirty and then prompt the user. Probably don't want a static popup every time someone closes unless the page really is dirty otherwise users will start to ignore the prompt.

              How to go about setting up the variable check within the onbeforeunload event isn't apparent to me. I'd have to figure it out.
              Mike Brown - Contact Me
              Programmatic Technologies, LLC
              Programmatic-Technologies.com
              Independent Developer & Consultant​​

              Comment


                #8
                Re: Stop the user from exiting without saving on a UX in an a5w page

                I had spent a lot of time looking at how to prevent users from accidently leaving my web page without saving data. There are a number of ways the user might close the form/browser that are very difficult to do anything about. Pete's suggestion of tracking the mouse nearing the browser's main close button is quite interesting.

                If you research the history of browser changes to the OnBeforeUnload event Jerry mentioned, you will see the programmers that create Web browsers are really at war with application developers. We want to help our users with nice applications that mimic what the users used to do with their desktop applications. The browser developers dont' care about that.

                Look at how Google Docs works and how many of the MS Window option dialogs work - the new philosophy is to remove the "Save" button and just to immediately save every change the user makes, without question and especially without user consent. How this new philosophy translates into database apps that can provide unlimited "undo" operations is a real pain.

                Oh, and having an updateable LIST on a UX that has:
                save details back to list
                save list to local storage
                push edits from list back to server

                Comment


                  #9
                  Re: Stop the user from exiting without saving on a UX in an a5w page

                  The tabbed UI uses the body "onbeforeunload" event to call a JavaScript function. That function finds the object pointer for every grid on the tabbedUI and uses some code to call a function on the grid to check if the grid is dirty.

                  Comment


                    #10
                    Re: Stop the user from exiting without saving on a UX in an a5w page

                    There are no full proof ways to do this due to security concerns. There are several good suggestions here though and we have used all of them to some degree. One additional option which we have used as well is to work on the user "focus". As soon as the data item is dirty you can disable all other controls within the user interface and deliver a msg to the user that they must save the data in order to proceed.

                    Comment

                    Working...
                    X