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

Closing popups

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

    #16
    Re: Closing popups

    In the case of a submit button, I would avoid putting the close window JS directly in the client-site submit button click event, as I expect this is going to close the window whether the save is successful or not?

    I'm assuming you don't want to close the window if there is some sort of validation error, or the the submit is unsuccessful?

    Assuming you're using server-side AfterDialogValidate event to call action scripting save submitted data to tables, take a look at the editor for this action script and use the "After Save Succeeded Javascript". Use this to call your close window JS... something like:

    // close window
    var ele = {dialog.Object}.getPointer('BUTTON_SUBMIT');
    {dialog.Object}.closeContainerWindow(ele);

    Comment


      #17
      Re: Closing popups

      Hi Robert,

      Thanks for the excellent tip, using the server side event, to generate javascript to send back to the client

      I'm reading all those comments in the server-side events more closely now!

      So what I have done is updated my client-side Submit button Click event, so it is now just one line again
      Code:
      {dialog.object}.submit();
      And as you suggested, I've edited server-side AfterDialogValidate event

      I am now also using a server side test of the value for
      rtc.flagRecordWasSaved

      Code:
      ExecuteServerSideAction("Save Data::Save_Submitted_Data_to_Table_s_")
      
      if rtc.flagRecordWasSaved then
      	e.javascript = e.javascript + crlf() + "alert('Data was saved');"
      	e.javascript = e.javascript + crlf() + "var ele = {dialog.Object}.getPointer('BUTTON_SUBMIT');"
      	e.javascript = e.javascript + crlf() + "{dialog.Object}.closeContainerWindow(ele);"
      else
      	e.javascript = e.javascript + crlf() + "alert('Did not save, please click the Save Data button once again!');"
      end if
      the alerts proved that rtc.flagRecordWasSaved is working as expected.

      I took my SQL Server offline while I was mid-edit in the browser popup window, and got the second alert when clicking the Submit button

      Then I bought my SQL Server back online again, and the data saved successfully when clicking Submit

      cool

      Comment


        #18
        Re: Closing popups

        also, check out the spot in the action script editor "After save succeeded Javascript". Put your JS here, and you don't have to even test if the save worked.

        shot.png

        Comment


          #19
          Re: Closing popups

          Robert, that's excellent!

          I did go looking for "After save succeeded Javascript" but I didn't find it the first time because I was looking in the wrong place.

          With that screen capture I now see exactly what you meant.

          That way you indicated is much nicer, entering the javascript directly into that client side event property

          instead of how I was doing it, adding it inside the xbasic e.javascript string

          e.javascript = e.javascript + crlf() + ...javascript...


          Also saves xbasic coding by not having to check the rtc.flagRecordWasSaved value

          Thank you for sharing your knowledge!

          Comment


            #20
            Re: Closing popups

            If you are opening the UX from a button or hyperlink from a Grid or UX, you can uncheck this option in the Action Javascript.
            Attached Files
            Steve Wood
            See my profile on IADN

            Comment


              #21
              Re: Closing popups

              Great thread! Thanks everyone for sharing the tips. Should save all of us a lot of headaches in the future.
              Brad Weaver, President
              ComputerAid International
              Ottawa ON Canada
              Versailles KY USA
              www.compuaid.com

              Comment

              Working...
              X