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

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

Why inline-javascript code fires before ajax callback UDF xbasic code?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Why inline-javascript code fires before ajax callback UDF xbasic code?

    Why inline-javascript code fires before finishes ajax callback UDF xbasic code?
    Sample test - button on onClick event:
    * first: ajax callback function. UDF sets new value for field (e._set function)
    * Second: inline-javascript shows up message with field new value (javascript alert function)

    Result: First is the message with old value(inline-javascript). When we close the message, the field value changes to UDF's seted value (ajax callback).

    How to fire inline-javascript commands "AFTER" finished ajax callback xbasic UDF?

    Please help,
    EDViNs
    p.s. Because of this situation I'm loosing big client right now, he want to switch to another technology and not to use A5...

    #2
    Re: Why inline-javascript code fires before ajax callback UDF xbasic code?

    This happens because the browser knows nothing of the code being executed on the server. As soon as the javascript is executed to initiate the callback, the second action fires (your javascript alert).

    To have the alert happen after the callback is complete, your xbasic function needs to return the javascript for the alert.

    Code:
    FUNCTION your_xbasic_function AS C (e as p)
    .... (your xbasic code here)...
    your_xbasic_function = "alert('Hi. Your ajax callback is complete.');"
    END FUNCTION

    Comment


      #3
      Re: Why inline-javascript code fires before ajax callback UDF xbasic code?

      My UDF:
      function test_a as c (e as p)
      e._set.Item_ID.value="TestItemID"

      test_a = "{grid.Object}.detailViewRefresh(); alert('Value: " + js_escape(e._currentRowDataNew.Item_ID) + "');"
      end function
      Result:
      First appiers message with old value, when I close message appiers new field's value.

      The same case if I do server side SQL selection and calculations in UDF in result on onClick or onBlur events first will be javascript form UDF's end and then xbasic code.
      Cace with detail view submit. I cant calculate things on server side, becouse detailviews submit will submit old "new" values.

      Looking for help,
      EDViNs
      p.s.Did somthing like this hapens normaly? If it's not usal case, did I need reinstall my A5?
      Last edited by eritovs; 10-28-2010, 11:18 AM.

      Comment


        #4
        Re: Why inline-javascript code fires before ajax callback UDF xbasic code?

        I'm not sure I follow you...sorry.

        However, be aware that detailViewRefresh() is also an ajax callback. You are encountering the same problem: your alert is firing before the refresh is complete.

        At this point things are happening in this order (at the browser level):
        1. Your user-defined callback is initiated
        2. The detailViewRefresh() callback is initiated.
        3. Alert is displayed.
        4. Javascript is executed to display new value(s) in detail view (but ONLY after you clear the js alert).

        Comment


          #5
          Re: Why inline-javascript code fires before ajax callback UDF xbasic code?

          Ok, I got Idea,
          but how about my main case with returning javascript "{grid.Object}.submitDetailView();"?
          The jawascript detail view submit submits old values.

          In Firebug report I find out that there are my sql selections, calculations, field set values and field submit with "OLD" NEW values, but not with calculated "NEW" values what was seted in xbasic with e._set.
          Where here is Detail View's refresh?

          After I just downgraded UDF for testing purpose till set field value and popup message with "NEW" value.
          Last edited by eritovs; 10-28-2010, 12:18 PM.

          Comment


            #6
            Re: Why inline-javascript code fires before ajax callback UDF xbasic code?

            Is there possibility to switch off or append alpha five's detailViewRefresh() callback initiation or possibility to wait for firing JavaScript code part?

            For Submit button I will test:
            At the UDF xbasic code end I'll add depending on detail view's row number do SQL Insert or Update. In result I will have correct data on server side.
            But then I still need think how to refresh grid and go to correct row and set focus on detail view's correct field after fired server side xbasic code.
            Yes, still problems on client side.


            Please help,
            EDViNs
            Last edited by eritovs; 10-29-2010, 06:38 AM.

            Comment


              #7
              Re: Why inline-javascript code fires before ajax callback UDF xbasic code?

              Let the ajax call complete and do the refresh in the afterAjaxCallComplete event(), otherwise your grid refresh is worthless.

              regards

              Wolfgang

              Comment

              Working...
              X