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

variable scope

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

    variable scope

    Let's hope that this is a simple question.....
    I am having trouble visualizing (or understanding) the scope 'session'. The book says "A window is open"......
    How is a 'window' opened or closed????????
    I understand the changing of layouts (forms or browses).

    D

    #2
    RE: variable scope

    You can either use Xbasic or action scription to create a script or action to open a form and /or close the form.


    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: variable scope

      If you are talking about global variables the session means the actual A5 program open used (It could be the Runtime or the Actual A5) to run the program on which the global variable was declare.

      if you are talking about regular variables they only survive until the script, form, browse in which it was declare.

      So think of session as the object(Form, script, browse) in which you declared the variable. except in the case of global variables where the session means the A5 program itself.

      If you have been dealing with Xdialog for a while here is the Pseudocode to my answer.

      if reg_variable then
      session=object_declared_in
      else
      reg_variable=global
      session=:A5
      end if

      Lately I have been talking Pseudocode to anyone, my wife already told me:

      if Mexican=Pseudocode then
      script_play(wife_gone)
      end if

      Have a nice one

      The Mexican
      The Mexican

      Comment


        #4
        RE: variable scope

        No problem with the forms, just the definition of the variable scope 'session'. When does a 'session variable' disappear??

        D

        Comment


          #5
          RE: variable scope

          OK then how does a 'local' variable differ from a 'session' variable???
          D

          Comment


            #6
            RE: variable scope

            From the Xbasic reference manual:

            A Session variable is visible to a form and all sub-forms and sub-browses in that form. A Layout variable is only visible on the form for which it is defined. For example, a layoutvariable defined on a form that is used as a sub-form is not visible to the parent form. A Session variable used on the sub-form is visible to the parent form.

            A form can refer to another form�s Layout or Shared variables by first getting a pointer to the variables. See "Getting a Pointer to Variables in another Namespace" below for details.
            =====================================

            Declaring Local Variables

            A variable that is implicitly declared in a script is valid only while the script is running. When the script is done, the variable disappears and is not available to other scripts or other parts of an application (unless the script that creates the variables is executed using the
            script_play_local() function). Variables of this sort are called local variables because they are restricted to the context in which they are defined. Variables implicitly declared within a user32 Alpha Five Xbasic Reference Manual
            defined function, or declared as function parameters, are also local variables. These variables are available to only the function, and are destroyed when the function is completed.

            kenn
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment


              #7
              RE: variable scope

              Thanx Kenn--
              The area you quoted was 'just below' the place I stopped while pondering the 'scope' of things...
              If I had continued reading, I would have seen the description and it might have helped..

              Again
              Thanx
              D

              Comment

              Working...
              X