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



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

onBeforePanelActivate Fires after Cilent-Side Validation

  • Filter
  • Time
  • Show
Clear All
new posts

  • onBeforePanelActivate Fires after Cilent-Side Validation

    I have a attached simple UX to demonstrate this.

    There is a PanelLayout, with a PanelNavigator and a PanelCard, and a TextBox control.

    The textbox has ValidationRules set to "Require Value"

    In PANELNAVIGATOR_1, onBeforePanelActivate event I added alert('onBeforePanelActivate');

    When the textbox becomes dirty, the validation fires and the alert fires.

    Am I doing something wrong, or is this a bug?

    Build 5887-5315
    Attached Files

  • #2
    Re: onBeforePanelActivate Fires after Cilent-Side Validation

    Looks like a bug to me.

    To be more specific about your test... it's not when the textbox becomes dirty. It's when you click into the textbox, and then tab out of the textbox... without entering anything into the textbox.

    Since the textbox is set to "Require Value", you get an error message in red about the text... and onBeforePanelActivate fires. Sometimes the textbox error happens first... sometimes the onBeforePanelActivate happens first... it's a toss up which fires first.

    There should be no relationship between textbox validation and onBeforePanelActivate. onBeforePanelActivate should not be firing since there is no other Panel to go to.


    • #3
      Re: onBeforePanelActivate Fires after Cilent-Side Validation

      Bug report submitted.


      • #4
        Re: onBeforePanelActivate Fires after Cilent-Side Validation

        I think I just found the same sort of thing, but in my case, I am getting stuck on in a textbox that has no type of validation configured. Also testing my app with build 5887-5315.

        I have console.log'ing in each of my Panel navigator "PanelActivate" events and I only see the onBeforePanelActivate event getting triggered. I don't understand this because none of the code involving this textbox has anything to do with navigating to a different panel.

        Thanks for having submitted a bug report for us.


        • #5
          Re: onBeforePanelActivate Fires after Cilent-Side Validation

          Below is Selwyn's reply to my bug report. I have not yet tried to see if his solution will work in my app, because I believe that if onBeforePanelActivate fires, the onSwipe event for the PanelCard does not fire. So I need to work on it.

          From Selwyn:
          ...there is an easy change you can make to your code to achieve this

          if(this.state.activePanel != arguments[0]) {
          return true;

          it is "sort of" a bug.

          there is built in code in the UX to set focus to the control where an error has occurred.

          for example, imagine a ux with two panel cards inside a panel navigator.

          say that Card 1 has a control called "text1" and it has a rule that says must not be blank.

          say that Card 2 has a submit button.

          say you run the component, leave the control on Card 1 empty, go to Card 2 and hit the submit button.

          this will cause a validation error (on the text1 control on Card1), but focus will be on Card2.
          so we set focus back to Card 1 so that you can see the error.

          the bug is that we should enhance the UX so that the panel navigate events do not fire if you set the active panel to a panel that already has focus.


          • #6
            Re: onBeforePanelActivate Fires after Cilent-Side Validation

            I am not sure of which events should fire, and in what order, between the PanelCard and the PanelNavigator. I would like to know.


            • #7
              Re: onBeforePanelActivate Fires after Cilent-Side Validation

              The order of events isn't documented... should be.

              It's fairly easy to find out. For each of the events in a Panel Navigator and PanelCard put code like this... detailing each event.

              console.log('PN1 onCreate');
              console.log('PC1 onCreate');
              For a simple UX, 1 PanelNavigator, 1 PanelCard, this is the order of events for just the UX displaying. onSize is firing a lot because I'm viewing the console.
              It's interesting that the PanelNavigator is firing after the PanelCard.



              • #8
                Re: onBeforePanelActivate Fires after Cilent-Side Validation

                I solved my issue.

                I need the controls in a particular panel to be validated client-side. Some of the validation is conditional on values in other controls, so I am firing validation code in the onSwipe event of the panelcard.

                Then if the validation has no errors, I have code in the panelnavigator onBeforePanelActivate that fires an xbasic function to save the values to a table.

                The problem was that I was using javascript alerts to determine if events were firing.

                Using the console.log as David posted (thank you David) shows that when a the user swipes, the onBeforePanelActivate fires before the onSwipe event.

                If there is an alert in onBeforePanelActivate , it will prevent the onSwipe event from firing.

                So the alert itself was causing my issue.