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

Event sequence

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

    Event sequence

    I am having difficulty understanding the why some events fire when they do. My form is called Patient_main and all the objects below appear on the form. This sequence of events is created from just opening the form from the control panel and then closing the form by pressing BUTTONCLOSE.

    This sequence of events is from the trace window. Can any one explain why the CanArrive events fire for objects without my clicking on the object and why the OnInit and OnFetch events fire for the browses before a record is fetched? Even more confusing why do the OnInit and OnFetch events of the form fire when no record is fetched?

    I'm trying to use the OnFetch evemt to control the appearance of the form Patient_main and since the event fires before a record is actually fetched it messes up.

    All help at enlightening my understanding is appreciated.

    Event: :Patient_main:BROWSE1 "OnInit"
    Event: :Patient_main:BROWSE2 "OnInit"
    Event: :Patient_main "OnInit"
    Event: :Patient_main "OnFetch"
    Event: :Patient_main:BUTTONADD "CanArrive"
    Event: :Patient_main:BROWSE2 "OnFetch"
    Event: :Patient_main:BUTTONADD "CanArrive"
    Event: :Patient_main:BUTTONADD "OnArrive"
    Event: :Patient_main "OnActivate"
    Event: :Patient_main:BUTTONCLOSE "CanArrive"
    Event: :Patient_main:BUTTONADD "CanDepart"
    Event: :Patient_main:BUTTONADD "OnDepart"
    Event: :Patient_main:BUTTONCLOSE "OnArrive"
    Event: :Patient_main:BUTTONCLOSE "OnPush"
    Event: :Patient_main "OnDeactivate"
    Event: :Patient_main "OnExit"
    Event: :Patient_main:BUTTONCLOSE "OnDepart"
    Event: :Patient_main:BROWSE1 "OnExit"
    Event: :Patient_main:BROWSE2 "OnExit"
    Tags: None
    #2
    RE: Event sequence

    Ohlen

    Some events do fire at odd times, but since this logic is built into the system, there is little we can do other than a workaround. What has worked in some cases is to trap the active object name or another condition in the event code. If the event fires when focus is on the "wrong" event or condition, just end the script.

    For instance, the CanArrive event fires for a field is there is a lookup defined when the lookup opens, but before the field is actually in change mode. You could trap the mode of the form and change how to react to the event based on that. Messy, but it works

    Jerry

    Comment

      #3
      RE: Event sequence

      Ohlen,

      I can't answer specifically, but I have learned that Windows itself fires oodles (pardon the technical term) of events almost continuously. The events we can use in Xbasic are a small handful of all that the operating system is generating. Each object on a form is, itself a window, and must be processed by the operating system, as it's drawn, generating more event messages, I suspect that some of these objects, especially those which are bound to the underlying data tables, require that the table be opened and a record 'fetched' each time the form opens. If the form is based on a set of tables, then the process repeats for each table in the set.

      -- tom

      Comment

      Previous template Next
      Working...
      X