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

Problems with arguments

  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems with arguments

    I am currently developing a mobile UX running version

    I have a character argument '_B_TROLLEY' that i set at run time i.e. {dialog.object}.setArgumentValue('_B_TROLLEY', 'TR-12345');

    When i click an embedded button in a list my argument gets reset to '__not_set__'.

    I have also noticed when i try and set an argument in either the onRenderComplete or onInitializeComplete events again i lose the value and it gets set to '__not_set__'.

    If anyone has experienced arguments losing their values please let me know and any suggested solutions would be gratefully received.

    Many thanks

  • #2
    Re: Problems with arguments

    Alpha doesn't include Version #'s in releases. What Build are you using... found right next to the version #?
    Is this a Web Mobile App or a PhoneGap Build Mobile App?
    I've never seen Alpha use '__not_set__'... where is that coming from?
    When you write "When I click an embedded button"... do you mean Alpha is resetting the value... or you are?
    How are you using the Argument? In a List Control?

    You must create a UX Argument, using Set value at runtime, but don't set it's value. You can do this either through the List Control Data Source tab, or UX Properties. Now .setArgumentValue has something to work with.

    If you're using the argument in a List Control... then you're running into a timing issue. The List is getting set up before the argument is set.
    You'd need to "Delay render til explicit refresh", and then .refreshListData() in onRenderComplete.


    • #3
      Re: Problems with arguments

      It sounds like you didn't create the argument first to me. Have you been able to succesfully create any argument and get it to work in any capacity?


      • #4
        Re: Problems with arguments

        I have fixed the problem by recreating the list control from scratch, which sadly does not help me understand why this was happening.

        This is a Web Mobile App, which i will eventually convert to a PhoneGap. The value "__not_set__" appears in chrome tools when debugging (i usually set a watch to see the arguments being set at runtime.

        The buttons i added were just extra fields on the list and they in turn call a JavaScript function client side.

        I always have "Delay render til explicit refresh" and i always set arguments at runtime.


        • #5
          Re: Problems with arguments

          Yes, I saw a similar problem today with Arguments in a UX. A UX that used to work just fine, stopped working when I turned on the "Pre-render component at design time".

          My UX starts a callback to the server during the client-side "afterPrepare" event and today I noticed right before the callback that Alpha was wiping out the argument variables on the client-side. Here's a section of that bad code:

          "__args_c_gPrAboutNM": "__notSet__", 	
          "__args_c_gTeTitle": "__notSet__", 	
          "__args_d_gDoEndDt": "__notSet__", 	
          } );
          I found two solutions:
          1) the obvious one - turn "Pre-render" off, or
          2) delay the callback by wrapping it in a setTimeout of 100 ms.

          I don't know that a 100ms delay will always be enough, though.

          I might just turn off the pre-render if there is not enough performance gain measured from the stress test that I am doing.
          Last edited by RichCPT; 05-06-2019, 11:31 PM. Reason: BBS truncated my orginal post