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

Form CanDepart Event

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

    Form CanDepart Event

    Is anyone else experiencing this? In a form, when I tab out of a field, the following field's CanArrive event fires before the current field's CanDepart event fires. (using Msgbox)
    Ernie

    Build 3272-3589
    Tags: None
    #2
    Re: Form CanDepart Event

    A more accurate method to determine the exact sequence of events firing is to enable event tracing in the trace window. Have you tried that?

    Comment

      #3
      Re: Form CanDepart Event

      No I haven't. Will look into doing that. Have never used the Trace window for debugging, but something I need to do.
      Ernie

      Later: Evidently this is the sequence of the events firing, which makes no sense to me. Another one of the needed workarounds.
      http://msgboard.alphasoftware.com/al...ad.php?t=54588

      Comment

        #4
        Re: Form CanDepart Event

        Tom,
        Is there a reason behind this sequence?

        Comment

          #5
          Re: Form CanDepart Event

          Ernie

          I have attached the sequence order from the Wiki on moving from field to field

          To see other sequence orders see this in the wiki

          http://wiki.alphasoftware.com/Object+Events

          FWIW

          Tom Baker

          Comment

            #6
            Re: Form CanDepart Event

            Yes, Tom. I have looked at that. However, before Event #6 fires on the current field, Event #2 fires on the following field. What is the logic in this?
            Ernie

            Comment

              #7
              Re: Form CanDepart Event

              Ernie, in addition to all the listed events, and their theoretical order of firing, there is another hidden aspect - often these events will fire more than one time. And if you have code in the events you sometimes have to use a technique Selwyn came up with way back maybe 1999 - namely, define a logical golbal variable called busy

              at a field objects event, for example you can do something like this:

              Code:
              if busy
     end
end if 
busy=.t.
     'do something with code
busy=.f.
              you sometimes have to toy with it - like reset busy to .f. at the ondepart event
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment

                #8
                Re: Form CanDepart Event

                Thanks for the suggestion, Martin. I have noticed sometimes when I have a popup message based on some criteria, it comes up more than once and figured this must be happening.
                Ernie

                Comment

                  #9
                  Re: Form CanDepart Event

                  The firing sequence is correct even though it seems illogical and counter-intuitive.

                  Logic dictates that you leave the current field before you arrive at the next. And therein lies the problem, that is you are using logic, logic that applies to humans not to alpha as in, logically speaking, you would first walk out of one place before you arrive at another place.

                  Not so. Maybe in human's logic, but not in computer's logic.

                  The idea is simple:
                  You do not know (that is, alpha does not know) that you walked out of one place UNTIL you get to the other place. The field does not loose focus, UNTIL another object gets focus. So, getting to the other place, contrary to logic and reason, occurs before you leave the first place.
                  Twisted logic maybe, but unfortunately alpha has no eyes to see nor mind to know that you are leaving the first object. It knows that you DID leave the first object only AFTER you arrive at the next object.

                  Comment

                    #10
                    Re: Form CanDepart Event

                    Thanks for the explanation, G. I figured there must be an illogical explanation for this.
                    Ernie

                    Comment

                    Previous template Next
                    Working...
                    X