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

Setting arbitrary message in transient message

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

    Setting arbitrary message in transient message

    I'm a rookie at JavaScript, so I need someone who is better to look at this.
    I'd like to switch from alert messages to transient messages to let the user know what happened in Xbasic processing. This is a web application.
    The processing can create a variety of error messages, so I was wondering, if there was an error, could I put the error message in a state variable, then display that in the transient message. Something like
    In Xbasic
    if pResult.error = .F.
    RecentlyViewed = "{grid.object}.runAction('RecentlyViewedSuccess');"
    else
    e._state.MyErrMsg = pResult.message
    RecentlyViewed = "{grid.object}.runAction('RecentlyViewedFailed');"
    end if

    Then in the JavaScript action 'RecentlyVIewedFailed'
    var stateInfo = {grid.object).stateInfo;
    var _MyErrMsg = stateInfo["MyErrMsg"]


    var _html = '<div style="display:inline-block;">'_MyErrMsg'</div>';
    var _options = {


    Could this work?
    Thanks,
    Pat Bremkamp
    MindKicks Consulting

    #2
    Re: Setting arbitrary message in transient message

    This is hopeful....
    To get past the error checking, I has to change to var _html = '<div style="display:inline-block;">_MyErrMsg</div>';

    and it displays the trainsient message "_MrErrMsg" in red. So I just need to get it to show the value of _MyErrMsg instead of the name.

    Pat
    Pat Bremkamp
    MindKicks Consulting

    Comment


      #3
      Re: Setting arbitrary message in transient message

      Your _MyErrMsg is being treated as static text because it's inside the single quotes. Try...

      Code:
      var _html = '<div style="display:inline-block;">' + _MyErrMsg + '</div>';

      Comment


        #4
        Re: Setting arbitrary message in transient message

        Thanks, David, that worked to put the text into the message, but I couldn't get the state variable to work, I'm giving up. What I'm trying to achieve is not worth all this trouble.
        Pat Bremkamp
        MindKicks Consulting

        Comment


          #5
          Re: Setting arbitrary message in transient message

          If you run your process twice you will find that the state variable is available the second time around. You're working with a Grid which is years behind in testing and compatibility with the rest of Alpha.

          If you run the same process in a UX component, you'll find it works exactly the way you'd expect... the state variable is set at the server and is available in the client. Not so with a Grid component... Alpha at it's best... very little consistency. This kind of stuff waste such vast amounts of time for developers.

          If you can live without running an Action, then you can accomplish what you want without involving a flakey state variable.

          Instead, return a call to a Javascript function... and you can pass in your error message.

          In your XBasic...

          Code:
          RecentlyViewed = "RecentlyViewedFailed('" + pResult.message + "');"
          The Javascript function will be...

          Code:
          function RecentlyViewedFailed(MyErrMsg) {
          
          	var _html = '<div style="display:inline-block;">' + MyErrMsg + '</div>';
          
          }
          This Javascript function will go into the Javascript Functions sections of your Grid.
          Last edited by Davidk; February 04, 2019, 12:20 PM.

          Comment


            #6
            Re: Setting arbitrary message in transient message

            David, that's a great idea. The only reason for the state variable was to get the message into JavaScript. This is a much better way and much cleaner. Thanks.
            Pat Bremkamp
            MindKicks Consulting

            Comment


              #7
              Re: Setting arbitrary message in transient message

              WooHoo! That worked beautifully! Looks like this...

              Failed_Message.png
              Pat Bremkamp
              MindKicks Consulting

              Comment


                #8
                Re: Setting arbitrary message in transient message

                Originally posted by Davidk View Post
                If you run your process twice you will find that the state variable is available the second time around.
                Sorry for jumping in on this solved issue, but I wanted to add my 2 cents:

                I sent in an official bug report a couple years back about State variables not being initialized soon enough when rendering a Grid. The issue Pat found about a state variable not being available when expected is similar. I had to put a check in my code such that if the state variable was undefined then the code would not do anything. In my case the AA JS library would automatically call my code twice anyway. The second time around the state variable existed. Without the check for existence of the state variable the JS would get an error and not run any other JS for that event.

                I like David's solution of returning all the JavaScript at once.

                Comment

                Working...
                X