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

APPLAUNCHER ---> how to close child UX ?

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

    APPLAUNCHER ---> how to close child UX ?

    I have a simple "applauncher" with a basic login control.
    this subsequently opened up a UX component according
    to the expression set in Applauncher, where mobile device opened UX
    and while pc-browser opened up a different UX

    All these working perfectly as it intended.....

    Now, I have been trying to find way to close either of the "UX"
    using these :

    {dialog.object}.logout();

    and expect the UX to close and bring me back to the applauncher's log in screen.

    what am I supposed to use to close the UX's ?

    appreciate your comment
    thanks

    bbb.png

    #2
    Re: APPLAUNCHER ---> how to close child UX ?

    ..
    Last edited by Ken Tjia; 12-02-2013, 12:43 PM.

    Comment


      #3
      Re: APPLAUNCHER ---> how to close child UX ?

      ..
      Last edited by Ken Tjia; 12-02-2013, 12:43 PM.

      Comment


        #4
        Re: APPLAUNCHER ---> how to close child UX ?

        ..
        Last edited by Ken Tjia; 12-02-2013, 12:42 PM.

        Comment


          #5
          Re: APPLAUNCHER ---> how to close child UX ?

          Apology to the community ...
          I got a working sample from Selwyn and proven the {dialog.object}.logout()
          indeed working perfectly ....


          MY UX NOT CLOSING, THE FIX is:
          I had to delete my UX and re-do it... & working perfectly.

          I believe my UX was originally set to have a login/logoff as a stand alone.
          then subsequently converted to using Applauncher. (this is just a speculation)

          FURTHER FOR THE ERROR FRO SERVER>>>
          I also had to "turned off"

          "startup component is loaded using a full page reload" was accidentally turned on
          that prompt the error ... shown on my post above.

          Thanks you everyone

          Comment


            #6
            Re: APPLAUNCHER ---> how to close child UX ?

            Ken

            You edited out all the fun of discovering the answer.

            The journey is sometimes more important than the destination.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #7
              Re: APPLAUNCHER ---> how to close child UX ?

              Yes Al, I deleted part of my post to make it simple to illustrate my issues
              I was all prepared to let this go away and move on to test more features.
              Convinced that I "mis-used" property/feature resulting ....
              but you get me back to think again... This option indeed should not have created such error ?

              The truth is I actually had created a smaller sets of components on the weekend and my problem remained.

              I ride along the idea to check this "full page reload" to yes ..... just now i read the announcement memo
              I indeed would like a re-load/refresh ... And that was the part that has consumed a week of my time.
              I was not along, had two other alpha's developers coaching along the last few days.

              So for now, I do not check this option, otherwise I would get this error.
              (shown at the beginning of my post)

              Thanks everyone again...
              I am not qualified to say any more .... it is working hi

              quote :

              Logout does a full page reload - When the user logs out, do you want this UX component to reload?
              If you check this option, the component's layout is re-computed on the server (and controls on the UX for which membership in security groups are required are hidden).
              Here is why this is an important property to understand:
              Assume that when you design the UX component you set the security property on certain controls in the component so that they are only visible to users who are in a certain group (i.e. security role). For example, you might have a button called 'Increase Salary' and you might have set the security on this button to only show the button for users who are in the 'Manager' group.
              Assume that the current user is logged in as a member of the 'Manager' group - so she sees this button.
              After this user logs out, you will want to ensure that this button is no longer visible. So, forcing the component to reload will cause the server to re-compute the layout of the UX component, and the button will be removed when the server sends back a re-rendered version of the component - because the user will no longer be logged in as a member of the 'Manager' group.

              Comment

              Working...
              X