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

helper functions in UX

  • Filter
  • Time
  • Show
Clear All
new posts

    helper functions in UX

    Can I get some pointers on using these helper functions in a UX component? As a simple example, I am trying to set the color of the text in a control by clicking a button.

    For instance, this example from the documentation does not appear to work in a UX component:

    /*Set the control's font family and font weight.*/
    $ss('firstname',{fontFamily: 'arial', fontWeight: 'bold'});

    /*The above example is a shortcut for this technique for setting the in-line style.*/
    var ele = $('firstname'); = 'arial'; = 'bold';
    Steve Wood
    See my profile on IADN

    Re: helper functions in UX

    It worked for me. Except that I used it directly in the DevTools console with my mobile app connected for debugging and entered:

    $ss('DLG1.V.R1.STATICTEXT_122',{fontFamily: 'arial', fontWeight: 'bold'});

    I saw the text immediately change style on the device.


      Re: helper functions in UX

      Thanks. I notified the document admin to update the docs for this page:

      I bet the helper functions are supposed to work on a UX but are not, at least in my attempt.
      Steve Wood
      See my profile on IADN


        Re: helper functions in UX

        Yes, the documentation should be fixed to reflect how to use those helper functions in Grids and UX's. Maybe they used to work as documented, but they sure do not now.

        Those 'helper' functions that begin with a "$" do not modify their first argument - the identifier of the control(s) to be modified.

        1) The identifier must be in the proper case - typically always uppercase.
        2) To locate the element by it's HTML "id" attribute the passed identifier must include the current alias for the UX/Grid and a row/instance number, or
        3) To locate the element by its HTML "name" attribute in a UX, you typically must prefix it with "V.R1." -- using the name attribute is not recommended, as there could be other UX's using the same "name" in its controls.


          Re: helper functions in UX

          Originally posted by Steve Wood View Post
          Thanks. I notified the document admin to update the docs for this page:

          I bet the helper functions are supposed to work on a UX but are not, at least in my attempt.
          Hello Steve,

          The Core Library functions work directly on HTML elements in the document. They will work with the UX and Grid, however you will need to build the full HTML id for those controls yourself or use the {dialog.object}.getPointer() method to get a pointer to the element (which can be used with core library functions.)

          In general, you should prefer to use the {dialog.object} methods to manipulate controls in a component and not the core library functions as the built-in {dialog.object} methods will trigger events and update component state while the core library functions do not.

          I do not believe there is a component equivalent for setting styles on an element, so in the case of $ss(), you can use {dialog.object}.getPointer() to get the element and pass it as the first parameter.

          We have added additional information to the Core library documentation about using the functions with components. You can see it here:
          Sarah Mitchell
          Director of Customer Success | [URL=""]Alpha Software Corporation[/URL]
          [B]Get in the know! [/B] Join us for our Weekly Webinars: [URL=""]TransForm Tuesday[/URL] and [URL=""]Wednesday's Alpha Anywhere Demo and Q&A[/URL]
          Connect with us: [URL=""]Instagram[/URL] | [URL=""]Twitter[/URL] | [URL=""]Facebook[/URL] | [URL=""]LinkedIn[/URL] | [URL=""]YouTube[/URL]