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

Show/Hide Expression & Prerendering

  • Filter
  • Time
  • Show
Clear All
new posts

  • Show/Hide Expression & Prerendering

    Web app running 5667.

    I'm using client-side show/hide expressions to show or hide various controls. When opening a prerendered UX the controls that should be hidden are very briefly shown to the user. Maybe 1/4 second. Then they disappear. If I turn prerender off and reload that same component it loads with the controls already hidden from view.

    Anyone else experience this? How do you deal with it? Do you just live with it?

    I'm trying to determine if this is a bug within Alpha or if I need to change how I'm showing/hiding controls. Briefly, I get the user's security group in an argument. I evaluate that argument in a JS function. Then return true/false. Sample code below...

    onDialogInitialize Server-side event
    dim p as p
    dim pUser as p
    dim sGroups as c = ""
    'Setup arguments
    sGroups = a5ws_get_user_assignments(pUser.userId)
    if is_one_of("Staff",sGroups) then
    	e.arguments[e.arguments.ArgumentNumber("ISSTAFF")].data = "True"
    end if

    JS Function
    function isStaff(){
    	var _arg = {dialog.object}.argumentValue('ISSTAFF');
    	if(_arg == 'True'){
    		return true;
    	} else {
    		return false;
    Ashampoo_Snap_Tuesday, October 15, 2019_12h32m54s_001_.png

    My hunch is I need to come up with a more efficient method. Suggestions/comments welcome as always.

    Thank you.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Independent Developer & Consultant

  • #2
    Re: Show/Hide Expression & Prerendering

    Maybe not more efficient, but rather how to get around what and when Alpha is doing stuff. It takes time for Alpha to figure out what it needs to do... particularly when dealing with a pre-rendered component.

    Instead of hiding the the control, if needed, show the control if needed. That way it will be hidden by default and only shown if all is ok.

    In your Client-side event onInitializeComplete add...

    This should hide your control right away... the user shouldn't get a glimpse of it.

    Now your arguments, functions, pre-rendered stuff has the time it needs to decide whether to hide or show the control.


    • #3
      Re: Show/Hide Expression & Prerendering

      That's a good idea. It never occurred to me to show a control when needed as opposed to hide.

      Thanks David!
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Independent Developer & Consultant


      • #4
        Re: Show/Hide Expression & Prerendering

        Yeah... the timing with Alpha is a bit of a crap shoot. You never really know what's going to fire when... until you go through it for a specific case.

        Although there is a "Hide" property, you cannot show that field using .setControlDisplay()... which is too bad.


        • #5
          Re: Show/Hide Expression & Prerendering

          I am confused about your statement:
          you cannot show that field using .setControlDisplay()... which is too bad.
          I just created a UX with three components:
          a sample text field, labeled 'sampleTextField'
          a "hide" button with: {Dialog.object}.setControlDisplay('sampleTextField',false);
          a "show" button with: {Dialog.object}.setControlDisplay('sampleTextField',true);

          The buttons work as expected. When the button is hidden with the "hide" button, it can then be shown with the "show" button.

          Am I misunderstanding you?

          Jay Talbott
          Lexington, KY


          • #6
            Re: Show/Hide Expression & Prerendering

            Yes... let me expand my statement...

            Although there is a "Hide" property for a control... if you use that Hide property to hide a control... you cannot then show that control using .setControlDisplay().