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

Detect if Component has been called from Another Component (embedded)

  • Filter
  • Time
  • Show
Clear All
new posts

  • Detect if Component has been called from Another Component (embedded)

    I would like to design modular components that are self standing (for example - that contain text boxes to allow selection of properties that will filter a list - that are only available when run in standalone manner) but which are otherwise used as embedded components. An example (in my case) is a list of rooms available in a given date range, to be called from a reservation entry component.

    Is there a property or method that can be evaluated so as to determine if the component is called from another component( so that DIV containing input text boxes may be hidden when not run standalone).

    Thanks in advance
    Mike Thomson

  • #2
    Re: Detect if Component has been called from Another Component (embedded)

    The following method will allow you to determine if the component is running standalone or embedded in another component:

    var pObj = {dialog.object}.getParentObject();
    if (pObj)
    // Running as an embedded component


    • #3
      Re: Detect if Component has been called from Another Component (embedded)

      Cheers Dave - your a champion!
      Mike Thomson


      • #4
        Re: Detect if Component has been called from Another Component (embedded)

        Further to this it seems that if you cannot embed a control that has a panel layout inside of the panel of another control that also has a panel layout.

        Any experience with this?
        Mike Thomson


        • #5
          Re: Detect if Component has been called from Another Component (embedded)

          I'm not sure exactly what you mean. Can you rephrase your question?


          • #6
            Re: Detect if Component has been called from Another Component (embedded)

            Thanks for your code DaveF, it helped me reference a Textbox on a parent UX, using javascript from a button inside an Embedded Object

            Mike can you map out your Design view tree? (maybe screenshots?)

            And is this another way to ask your question?
            Originally posted by Mike Thomson View Post
            Can you place an Embedded Object UX Component (that itself contains a panel navigator),
            inside a Panel Card of a Panel Navigator on a parent UX Component

            I have the following and it worked

            Parent UX Component that looks like this in Design View

            Panel Navigator
            -- Panel Card
            ---- Embedded Object (UX Component1)
            ---- PanelFooter
            ------ Textbox (variable name = EmpID)
            ---- PanelFooter End
            - Panel Card End
            Panel Navigator End

            The child Embedded Object (UX Component1) looks like this in Design View
            -- Panel Card
            ---- ButtonList
            ---- Button_1
            - Panel Card End


            and not directly related to your question, but to finish off with the reason I found this thread...

            DaveF's code helped me reference the Textbox on the parent, from inside the embedded child UX, like this

   javascript =

            var pObj = {dialog.object}.getParentObject();
            if (pObj)
            var empid = pObj.getPointer('EmpID');