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

Embedded Objects In Mobile App Causing Uncaught Reference Errors

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

    Embedded Objects In Mobile App Causing Uncaught Reference Errors

    Greetings Alpha Developers,

    I have been trying to determine why embedded UX components are throwing uncaught reference errors in one of the mobile apps I'm working on.

    Mobile app structure:
    Login_UX
    ___Main_UX
    ______Grandchild1_UX
    ______Grandchild2_UX
    ______Grandchild3_UX
    ______Grandchild4_UX

    The mobile app consists of a login UX component with a single embedded 'Main' UX component that has 'Delay render till visible' checked. When the initial login panel card is rendered, there aren't any errors. However once successfully logged in and the embedded 'Main' UX is rendered, any embedded UX components (grandchildren to the login UX) that are NOT set to delay render till visible throw the uncaught reference errors as shown below.

    Strangely enough, these errors don't seem to cause any issues with app performance. Furthermore, all objects listed as undefined seem to work normally which is why I have kept this as a back-burner issue so long.

    Per Google's JavaScript Console:
    Capture.PNG


    Any help getting these errors resolved without having to set all embedded components as Delay render till visible = true would be most appreciated.
    Thanks!
    Justin Taylor

    #2
    Re: Embedded Objects In Mobile App Causing Uncaught Reference Errors

    Do you have any code that references these objects? EG, {dialog.embeddedUX_[alias]}?
    Alpha Anywhere latest pre-release

    Comment


      #3
      Re: Embedded Objects In Mobile App Causing Uncaught Reference Errors

      Originally posted by TheSmitchell View Post
      Do you have any code that references these objects? EG, {dialog.embeddedUX_[alias]}?
      For interaction between these components(getting/setting values, calling runactions, etc) I typically create unique window variables onRenderComplete for each embedded object such as:
      Code:
      //create window variable so parent dialog can access values from this component
      window['Upload_Corrective_Images'] = '{dialog.object}';

      Comment


        #4
        Re: Embedded Objects In Mobile App Causing Uncaught Reference Errors

        In an effort to get a little more information on this issue I decided to pick one of the embedded components that throws the uncaught reference error and start removing controls one-by-one. I have found that once I remove the image control 'Photo_Image', this component no longer throws the error. Unfortunately as soon and I re-add the image control (even with a different variable name), I'm right back where I started with the component yet again throwing the error.

        While it does feel like this is a step in the right direction in terms of at least knowing specifically which control in the component is having issues, I'm still at a loss as to how to resolve this error since this mobile image upload component is really going to need that image control :P

        Here are some screenshots of the UX and the properties set for the image control
        Capture.PNGCapture2.PNGCapture3.PNG

        As always any fresh ideas would be most appreciated
        Thanks!
        Justin Taylor

        Comment


          #5
          Re: Embedded Objects In Mobile App Causing Uncaught Reference Errors

          I started thinking that this might be an Alpha bug so I successfully recreated this error with a simplified test case. Since Selwyn's first question is usually, "did you try the latest release?", I decided to do so first before creating a bug report. Low and behold, I have determined that this must be an Alpha bug associated with version 2614_4409 which seems to be resolved in 2689_4440.

          Thanks for reading!
          Justin Taylor

          Comment

          Working...
          X