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

Command to return to lable in action script?

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

    Command to return to lable in action script?

    Hi,
    Is there a way of having a button on a form which returns to a lable in the action script where the form was called from ?

    I have a form(a). That form has a button which calls a different form(b) I want a button on form(b) which returns command to a point, or lable, in the action script of the button on form(a)

    The idea is to avoid making several nearly identical forms, where the only difference is the scripting on the buttons.
    Any help will be greatly appreciated.

    Brian Dennis.

    #2
    RE: Command to return to lable in action script?

    Brian

    I am not quite sure what you are trying to do, but the simple answer is no. A label in a script exists only in that script, you can not reference it from any other script.

    Now, if you want to have multiple actions that can be run from a single button, this is not real difficult. The simplist way is to determine which part of the script to run based on some outside condition or variable. For example, if you have a shared or global variable, you can check the value of the variable and then go to a particular label posiion in the script. Lets say the variable is called "V_option" and can have a value of "A,B,or C". The following xbasic will send the action of the script to whatever label position you want.

    select
    case v_option = "A"
    goto label_a
    case v_option = "B"
    goto label_b
    case v_option = "C"
    goto label_c
    end select
    ' If v_option does not equal "A,B,or C", the script stops here
    end

    label_a:
    ' put in the code to run if the variable is equal to "A"
    end

    label_b:
    ' put in the code to run if the variable is equal to "B"
    end

    label_c:
    ' put in the code to run if the variable is equal to "C"
    end

    Jerry

    Comment


      #3
      RE: Command to return to lable in action script?

      Jerry,

      Thanks for the response.

      The advice about the "no" saved me a lot of trying to do something impossible - thanks.

      I have got around the problem in another way, but your suggestion of using variables sounds good for another situation which I will soon have. Thanks for your time.

      Brian.

      Comment


        #4
        RE: Command to return to lable in action script?

        Brian

        Another neat way to have multiple actions from a single script is to change the text displayed on the button and then check the text value and use that to determine which part of the script to run. For instance, you may have a button called "button_report" which can either preview a report or print a report. Another action may have the following code line to set the text on the button to show which action you want.

        parentform:button_report.text = "Preview Report"

        In the script on the button, test for the text on the button and use it in place of the variable.

        dim v_option as c

        v_option = parentform:button_report.text

        select
        case v_option = "Preview Report"
        goto label_a ' and so on


        Now you can use the rest of the script to send the action to the correct code. You may also want to change the text of the button from within the script to show the next possible action. The example here shows using the button text property, but actually, you could use almost any property for the object. In one case, I change the color and use the color to determine which code to run.

        Jerry

        Comment


          #5
          RE: Command to return to lable in action script?

          Jerry,

          That is a realy useful idea to me. Will be definitely used in my app. for our tool rental business in Portugal.
          I am making a app. in Alpha5 to replace the app I have in Alpha 4, which has grown up over approx 12 years. We have lots of situations when I really use the same form with different actions from that form - to enter info of a client, alter info, look at info, etc, all use practically the same form; your idea makes the whole app. lots easier as I think of it now.

          Thanks,

          Brian

          Comment


            #6
            RE: Command to return to lable in action script?

            Brian

            There are a number of ways you can set up the values for the button text, etc. If you are opening the form from another screen, one nice way is to load the form first, set the button text values, and then show the form. For example, if your form is called "customers" and in this instance you want a button called "button_Print" to have the text "Preview Report" , the following will work

            frm = :Form.load("Inventory")
            frm:button_print.text = "Preview Report"
            frm.show()
            frm.activate()

            If you wanted the text to read "Print Report, just change the code that loads to form to

            frm = :Form.load("Inventory")
            frm:button_print.text = "Print Report"
            frm.show()
            frm.activate()

            This method allows opening the same form with different settings so it can look like a different form. You can change any property for the form or form objects that can be set with xbasic, including hiding or showing certain objects.

            You could also test for the value of anything and rest the text based on that value. In one case, I test the value of a field in the displayed record. If it is one value, the button text is one text. If the field value is different, then the button text changes. I put the code on the form OnFetch event so it checks whenever a new record is fetched.

            Jerry

            Comment


              #7
              RE: Command to return to lable in action script?

              Jerry,
              You have certainly given me lots of ideas about using forms in ways I had not considered - thanks a lot.
              My app is a lot like that (tool rental business) where one form layout is used in many ways, eg: to enter client details, alter them, look at them, relate to another client, etc, and your ideas will enable me to use the same basic form is lots of diferent ways. It will also save me a lot of time, and let me spend more time getting the form looking and acting good and professional.
              My mindset was to have a different form for each situation, eg: just because a button on the form was needed to have a different action. Having an alternative idea is great.

              Thanks a lot,
              Brian.

              Comment

              Working...
              X