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
Devcon 2020 Goes Virtual! LEARN MORE >

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

dialog boxes

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    dialog boxes

    I have used action script to create a few dialog boxes. When a user selects Ok, the next step checks certain variables are filled. How do I stop the dialog from closing at this point. I have a message to say the error and I want it to simply close back to the dialog.

    I have read through help and can really only see the solution in having write the whole thing in script in xbasic (which I am a true noveice at the moment). Is there a way in action scripting for this?

    Thanks in advance
    Tags: None
    #2
    Re: dialog boxes

    Hi Mark,
    Is there a way in action scripting for this?
    Yes, have a look at Branch.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment

      #3
      Re: dialog boxes

      As Kieth said, the branching group will take you to "GotoLabel". The Branching command requires a character expression result and logical (value<>"") is not accepted. What you want is the "GotoLabel"

      When you press the OK button, the dialog closes. That is not avoidable. With the GotoLabel action script command, the sequence can be directed back to a point in the sequence based upon a condition (i.e. value = "") so that the dialog reopens, and will give the impression of "going back to the dialog", but it will actually be another generation of the dialog. Three things you need to be aware of. 1) the cursor will be at the starting point in the dialog, and 2) if you want the dialog variables to be populated with the values of the first attempt and show them in the reopening, the Label has to be positioned after any command that dims the variables to equal blank/0/null, and if not, before the command that blanks the variable. 3) There has to be an EndScript command with the condition: varC_result="cancel" immediately after the dialog action script command to end the script if the person presses the Cancel button. If not, you can get into a no escape loop.

      Good luck
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment

        #4
        Re: dialog boxes

        Hi Mike,

        Just as a matter of interest, I created a routine where I needed to make the GoToLabel happen a number of times based on a field value. Within that loop was a another routine that entered records to another table. The only xbasic was inline to say count=count+1.

        There is so much that be done with AS, its almost unbelievable.
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment

          #5
          Re: dialog boxes

          Hi Kieth,
          There is so much that be done with AS, its almost unbelievable.
          No doubt! I have several early applications almost completely developed with AS. As you, I used the Branch commands extensively! And I still rely extensively on the genie to generate scripts converted to XBasic as a starting point for reductions, amendments and additions.
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment

            #6
            Feedback

            Thanks for the help. I got it do it as you recommended with the goto label. This opens a whole new area for me as this allows for loops without script. I can add that I was able to also to allow the dialog to keep its new data entered in previous fields so at least the user does not have to enter again. It is a pitty about the ability to set focus back to the offending field in the dialog.

            In fact it would be good to be able to set focus on other fields at dialog startup as well as I often use the first field for a date which is default to today, but could be changed.

            Comment

              #7
              Re: dialog boxes

              Hi Mark,

              I think it is time for you to have a good look at Learning XDialog. This is in the Program Files A5V9 folder.

              Here you will see how to write code to create your own dialogs, also you will learn how to give or restrict focus to buttons and fields.
              Regards
              Keith Hubert
              Alpha Guild Member
              London.
              KHDB Management Systems
              Skype = keith.hubert


              For your day-to-day Needs, you Need an Alpha Database!

              Comment

                #8
                Re: dialog boxes

                I agree that is where I will end up, but I am cautious that once I do I will use script in preference to the built in power. I really am impressed with the A5 programmers approach to giving users more power without have to venture too deep into the script area. I am pushing my knowledge boundaries here if that makes sense. I have a lot of friends looking for an answer like A5, but really have no script knowledge at all. I will be showing the action script virtues to them

                Comment

                  #9
                  Re: dialog boxes

                  Mark,
                  but I am cautious that once I do I will use script in preference to the built in power
                  Nothing to be cautious about really! Use Action Script (AS) to create what is needed....but learn to use xbasic/xdialog to modify it to meet the specific requirements that AS cannot do (or cannot do as easily). I suppose once enough snippets/templates are saved for various xdialogs and such you might not use AS as much, but until then AS will have a place.

                  I use AS quite a bit for developing operations and then convert them to xbasic to tweak them to be more specific to the task I need...no way am I going to hand create an operation when AS can produce the framework so easily. AS is also a great tool to use to create your initial xdialogs.
                  Mike
                  __________________________________________
                  It is only when we forget all our learning that we begin to know.
                  It's not what you look at that matters, it's what you see.
                  Henry David Thoreau
                  __________________________________________



                  Comment

                  Previous template Next
                  Working...
                  X