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

UX access panel only once on login

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

    UX access panel only once on login

    After the user logs in she is presented with a panel with some button choices. When she makes a selection I want her to go to a new panel - with no way to get back to the first panel - until she logs out. IOW's login always presents Panel 1. They click a button and panel one goes way (gets hidden, whatever) and go to a new panel layout where they can navigate but are unable to go back to panel 1 no matter what. I'm sure this is simple enough, but I've watched bunches of videos and I don't see it jumping out at me. I tried wrapping a default container around or inside of Panel 1 with show/hide but Alpha doesn't like that. Does anyone know? Is there a video for this?
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com



    #2
    Re: UX access panel only once on login

    Do you intend to control all of the navigation using button clicks or do you want the user to be able to navigate from panel to panel by swiping left or right?

    Comment


      #3
      Re: UX access panel only once on login

      Dave,

      Once the user goes to panel 2 or whatever they will need the swipe ability as well as buttons.
      Peter
      AlphaBase Solutions, LLC

      [email protected]
      https://www.alphabasesolutions.com


      Comment


        #4
        Re: UX access panel only once on login

        Ok. You need to add a 2nd panel navigator around the 2nd panel card and whatever other panel cards you want in that group. The login panel card would be included in the main panel navigator at the top.

        Code:
        Panel Navigator 1
          Login Panel Card
          Panel Navigator 2
            Panel Card 2
            Panel Card 3
        Panel Navigator 1 should be a programmatic type and Panel Navigator 2 should be a carousel type. Panel cards inside the 2nd navigator cannot go back to the login panel card. Let me know if you need more details.

        Comment


          #5
          Re: UX access panel only once on login

          I think I found a way to do it. See Video 48 UX_V12. I'm using Selwyn's removePanel() function. I simplified the function for my case and call it from a button and it works. Now I'll find an event so that it is automatic.

          function removePanel() {
          var panelName = 'PANELCARD_1';
          var pNav = {dialog.object}.panelGet('PANELNAVIGATOR_1');
          pNav.removePanel(panelName);
          }
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: UX access panel only once on login

            Dave,

            In your method above does it make a difference that once the user logs in I call an embedded UX? Using embedded keeps it less cluttered and less confusing.
            Peter
            AlphaBase Solutions, LLC

            [email protected]
            https://www.alphabasesolutions.com


            Comment


              #7
              Re: UX access panel only once on login

              Peter,

              These methods should be used if you have an unknown number of panel cards. For example, if you had a design where a panel card represented one record and users could have 1 or more records in a table. Something more along those lines.

              Comment


                #8
                Re: UX access panel only once on login

                Nope. I use embedded UX's throughout all of my apps. They work very seamlessly.

                Code:
                Panel Navigator 1
                  Login Panel Card
                  Panel Navigator 2
                    Panel Card 2
                       Embedded UX

                Comment


                  #9
                  Re: UX access panel only once on login

                  Originally posted by DaveF View Post
                  These methods should be used if you have an unknown number of panel cards.
                  I'm confused? Do you mean your method or the function I posted above? Could you elaborate on the why & why not?

                  Thanks
                  Peter
                  AlphaBase Solutions, LLC

                  [email protected]
                  https://www.alphabasesolutions.com


                  Comment


                    #10
                    Re: UX access panel only once on login

                    Sorry, I was referring to adding and removing panel cards dynamically as demonstrated in Video 48 UX_V12. This just requires a lot more overhead at runtime which you don't need to do assuming you know up front how many panel cards your app is going to show. Since I do not understand the full scope of your app, this may be a good solution assuming users can have a variable number of panel cards.

                    Comment


                      #11
                      Re: UX access panel only once on login

                      I will have a fixed number of cards. But I don't see why the function presents any overhead? The function references one card only. However I may not be able to use the function since the navigator is a carousel type. The way it is now, users don't have to click the button to get to the next panel since they can swipe - which is not what I want. I want to force users to click a button before being able to go to the next panel. And then not be able to go back. But thereafter they should be able to swipe.
                      Peter
                      AlphaBase Solutions, LLC

                      [email protected]
                      https://www.alphabasesolutions.com


                      Comment


                        #12
                        Re: UX access panel only once on login

                        The following should work with an embedded UX. Panel Navigator 1 should be set to programmatic. Panel Navigator 1 in your child UX should be set to carousel if you want the user to be able to swipe left and right to navigate between panel cards. The user will not be able to navigate back to the parent UX's panel card 1.

                        Code:
                        Panel Navigator 1
                          Login Panel Card
                          Panel Card 2
                             Embedded UX

                        Comment


                          #13
                          Re: UX access panel only once on login

                          I'll experiment with your method. I'm still stumbling around the whole concept of panels, etc.
                          Thanks for all your help.
                          Peter
                          AlphaBase Solutions, LLC

                          [email protected]
                          https://www.alphabasesolutions.com


                          Comment


                            #14
                            Re: UX access panel only once on login

                            The tricky one to learn is the Panel Layout control. You can do some very complex navigation when you add this control to the mix.

                            Comment


                              #15
                              Re: UX access panel only once on login

                              I did already have the layout as per your posts #8 & 12.

                              I think what I really want is this:
                              Code:
                              Panel Navigator 1
                                Login Panel Card
                                Panel Card 2
                                 Button 1
                                 Button 2
                                 Button 3
                                Panel Navigator 2
                                  Panel Card 3
                                     Embedded UX
                              So:
                              User logs in
                              Panel Card 2 is displayed
                              User click Button 1, 2 or 3
                              Embedded UX is displayed
                              ---
                              They can't go back to panel card 2 until they logout & log back in.
                              Peter
                              AlphaBase Solutions, LLC

                              [email protected]
                              https://www.alphabasesolutions.com


                              Comment

                              Working...
                              X