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



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

V11 Dialog - Automatically save and restore state information best practice question.

  • Filter
  • Time
  • Show
Clear All
new posts

  • V11 Dialog - Automatically save and restore state information best practice question.

    I have a simple application. Two A5W pages with a dialog component in each of them. I fill out some data on the first page and then move to the second page. I use a session object to transfer elements to the second page. When I hit the back button on the browser, it goes to the first page, but the dialog component is refreshed to the default state (vs have the last state when the user was on that page.). I have thought of a couple of ways to handle it, but I wanted to get feedback from the group on the best practices.

    1) I could have two pages with a dialog on each one. Then I would put the code in the initialize event to restore the state from a session dialog.
    2) I could have both dialogs on the same page and then have some glue code that hides/displays the dialog depending on the status. I would have to write some code in the dialogs to call the page which would then control visibility.
    3) I could have a single dialog with two containers for the two "pages". And use the logic in the dialog to hide/display containers. (Simplest of the bunch...but I have concerns)

    NOTE: Both pages are fairly complex so one of my key concerns is download/load time for each of the pages. And....with a ton of components on a single page (from dual dialogs on a single page) I don't want to trigger strange problems with the browsers.


    1) Is there a simple way to store and then restore the state of a dialog component without having to right a lot of logic (i.e. I don't have to get a session variable and then update all of the controls on the dialog to set them to the original state.)
    2) If I go the two dialogs on one page, do I run the risk of long load times and/or performance issues because of the large set of components on a single page? Also, how would I structure the code to trigger the
    3) Ditto for two big containers in one dialog, long load times/performance issues?

    I know this one is a bit long...but will help me establish best practices for coding my web applications going forward. Thanks in advance.

  • #2
    Re: V11 Dialog - Automatically save and restore state information best practice quest

    What are you trying to achieve -- i.e. what is the business logic?

    Michael Carroll


    • #3
      Re: V11 Dialog - Automatically save and restore state information best practice quest

      Thanks Michael.

      The first page collects a bunch of data from the user. It then stores that data in a class, does some internal calculations and then puts that into a session variable. The second page then takes the object from the session variable, updates some online controls and then lets the user continue to do some other data collection activites that update the object.

      The key question is do I need to write the update/initialization code on the first page if the user uses the browser back button to navigate back to that page it looks the same as when they left it, or is there a simpler/better way where the dialog re-initializes the controls. The less code I write the better!