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

Javascript Row Events vs. System Events

  • Filter
  • Time
  • Show
Clear All
new posts

  • Javascript Row Events vs. System Events

    Whats the difference between "Javascript - Row Events onClick" and "Javascript - System Events onRowSelect" in a grid?

  • #2
    Re: Javascript Row Events vs. System Events

    I'm not sure, but it's probably a matter off timing, i.e. which is called first. Try putting an alert box in each (with different messages) and see which comes up first.
    Stephen Pilon
    Associate Librarian
    Christendom College


    • #3
      Re: Javascript Row Events vs. System Events

      Originally posted by StephenP View Post
      Try putting an alert box in each (with different messages) and see which comes up first.
      The System events onRowSelect gets called alot. It popped up a message when I saved the grid (in Alpha). Then again when I loaded the page with the grid (in browser). Then again when I clicked the row. Row Event's onClick NEVER got called. Bug?


      • #4
        Re: Javascript Row Events vs. System Events

        I put this in the System Events, onRowSelect:

        alert('Box 1: System Events - onRowSelect');
        and this in the Row Events - onClick:

        alert('Box 2: Row Event - onClick');
        When I start the grid, onRowSelect (i.e., Box 1) fires twice with the detail view showing on the page, once with detail view as pop-up.

        When I click on a row, onClick (Box 2) fires, then onRowSelect (Box 1) fires

        If I sort by clicking a column header, onRowSelect fires five times (with a 10 row view).

        I changed it to a 25 row view, and onRowSelect fired five times.

        In either of these last two cases, if the detail is pop-up, then onRowSelect fires four times.

        When I click the detail view link, onClick fires, then onRowSelect fires twice (presumably once for selecting the row, and once for selecting the detail--which is part of the same row)

        When looking at the detail view, if I select the Next or Previous record button, onRowSelect fires once, onClick does not fire.

        I think the answer to your question is that onClick fires only if the row is clicked on by the user, whereas onRowSelect fires whenever a row is selected by clicking, navigation, etc. Thus the names, eh?
        Stephen Pilon
        Associate Librarian
        Christendom College


        • #5
          Re: Javascript Row Events vs. System Events

          Great! You should write for the wiki ;)


          • #6
            Re: Javascript Row Events vs. System Events

            Here are the definition for each event:

            The onRowSelect client side grid system event fires when a Grid row is selected. it also fires when a row is selected for both read only and editable Grids.

            The Javascript onClick row event fires when the user clicks on a row.

            I think the reason why the onRowSelect event fires twice when the grid is started is because the 1st row of the grid is automatically selected when the grid loads or initialiazes so if you have 1 grid and a detail view you will get 2 onRowSelect events firing for each 1st row of the grid, and so on...

            I hope this helps