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

Bug & workaround: Getting pointers to child components in pop up windows

  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug & workaround: Getting pointers to child components in pop up windows

    I don't get onto this forum very often (not much to contribute) but this could help someone out

    I have used JS to set field values in UX components for a good while

    Recently I started having problems with child components opened in a pop up window
    I would do my usual code:

    var co = {dialog.Object}.getChildObject('CHILD1');

    co.setValue('MiddleText', 'John');

    (no error checking included)

    and it would either fail totally or would work for a few days and then fail

    very perplexing

    eventually I put a test case together and sent it to Alpha

    I have just received a short video from Selwyn explaining the problem and a workaround- thank goodness!

    So after getting Selwyn's permission to share his video here is a link:

  • #2
    Can I ask what build you are on and when the problems started?
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)


    • #3
      Hello Pete

      Happy to oblige

      I was using build 7776, in the course of trying to work out what was going on I also reverted to build 7295 and updated to 7902
      But the problem can occur in all of these builds

      I have had odd problems setting field values in child components for ages but I often work around it

      What is hard to get across is how frustratingly inconsistent this issue was and it seemed to be getting worse

      Mostly new components would fail at the start but sometimes work for days before failing and older components would work OK mostly

      I have used Alpha since 2008 but mostly not for web development which is by far my weakest skillset so when things don't work I generally blame myself first

      Eventually I used the demo component at https://documentation.alphasoftware....t%20Method.xml

      which worked fine at first but after a bunch of opening JS actions and saving them without changes it broke and I knew it wasn't me so sent it in as a bug report

      It is now obvious that Alpha at some point decides to rename child aliases but the inconsistency of when it does is baffling, at least to me


      • #4
        Another video from Selwyn...

        looks like the issue is fixed

        Whilst on the one hand it is frustrating that I have spent considerable time worrying over this it is pretty fantastic to get such interest in the problem and a swift resolution


        • #5
          But now you are left with another issue, which is, do you base your production app on the nightly build with the fix to this issue in it but which is not advised by Alpha and may cause other unknown issues, or do you wait for the next stable build which has the fix but may also cause unknown issues due to changes and new features. Maybe you will have to wait for a few stable builds until there is one that is found to be mostly stable? I think Alpha is causing developers to take the risk of using a nightly build. I really hope they implement what they discussed in Devcon which is to have a track that is only for fixes and a nightly build that has both. If anybody is listening I hope they take this to heart and put all other development on hold until they get this second track going.

          I only say this because I love Alpha Anywhere but the frustration and time consumption of figuring out if you are doing something wrong or if there is a bug, this has bitten me too many times.
          David Weinstein
          Best Tech
          [email protected]t


          • #6
            No I steer clear of the nightly builds

            I will use Selwyn's advice from the first video to fix my broken aliases and get these components working again

            In my opinion Alpha is an astonishing piece of software - the things I can build with it are amazing but sometimes using Alpha is like a game of Snakes & Ladders


            • #7
              I realized after this post that is what the issue has been for me all along. I have been struggling with UX components that would work the first time but not the second unless a complete refresh was done. Thanks for submitting the bug and thanks to selwyn for once again solving it!
              NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"