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 header problem with iPhone Safari

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

    UX header problem with iPhone Safari

    I have a UX list component that will access the corresponding details form by clicking on the row. The details form has a back button in the header. When you click on one of the text boxes in the details form (which opens the iPhone's keypad screen) then enter a value and click done the form gets pushed up and the header disappears. It also creates a blank footer at the bottom of the page instead. With the header gone, there's no way to go back because the button is not visible. If I scroll up and down then the whole screen moves but I can't get the header back and can't get rid of the blank footer at the bottom. Anyone have any idea what's going on?

    ***Update***
    The header issue happens every time I open the iPhone keypad from a textbox, dropdown, etc. on any form. The popup keypad pushes the header up out of view and creates a blank footer at the bottom. It appears to be an issue with the iPhone keypad and not necessarily the dialog (although there may be some setting I'm missing on all the dialogs). Any help would be appreciated.
    Last edited by TheDuke; 08-07-2013, 04:11 PM.

    #2
    Re: UX header problem with iPhone Safari

    ***Another Update***

    This must be a bug... I'm having the same issue when I publish the Demo Mobile App included with Alpha Anywhere. I'm not sure where to submit bug reports but I guess I'll find it. If someone could direct me that would be helpful.

    Comment


      #3
      Re: UX header problem with iPhone Safari

      Since this issue also exists with the demo mobile app it must be a bug. I submitted a bug report and hope to find out more.

      Comment


        #4
        Re: UX header problem with iPhone Safari

        I am experiencing the same issue. So far I haven't found a solution

        Comment


          #5
          Re: UX header problem with iPhone Safari

          Maybe there is some way to identify when the iPhone keypad is opened/closed and then do some sort of screen refresh.

          Comment


            #6
            Re: UX header problem with iPhone Safari

            David - Do you have "Body can scroll" checked in the Panelcard?

            Comment


              #7
              Re: UX header problem with iPhone Safari

              Dave,
              You have to have the 'body can scroll' option enabled else the fields on the dialog would run below the screen with no way to access them. In any event, I've tried it both ways and same problem. The issue happens whenever you tap on an input field to enter data where the control is half way or more down the screen so that when the iPhone keypad opens from the bottom it pushes the screen up to keep the field in view. It it easily reproduced on any panel that has input fields and a header at the top, including the demo mobile app included with A5v12.

              Comment


                #8
                Re: UX header problem with iPhone Safari

                Well, I just discovered that the problem only exists when you actually publish the app and put the startup UX on an index.a5w page. Everything works fine using the remote test. Strange.

                Comment


                  #9
                  Re: UX header problem with iPhone Safari

                  Well, through trial and error, I've solved this issue. Apparently, when you insert a UX component into an a5w page (in my case index.a5w) the source code that gets generated includes one or more   statements near the bottom of the page. I'm not an HTML expert but I presume there must be some incompatibilities amongst browsers using this statement as it was causing the issue described above.

                  Comment


                    #10
                    Re: UX header problem with iPhone Safari

                    I am experiencing the same issue as described above regarding the header being pushed up. Can you give me more specifics on how you solved the problem? I am a new Alpha user.

                    Comment


                      #11
                      Re: UX header problem with iPhone Safari

                      I found the issue. No need to respond. I am glad I found your post. Sometimes the fix is not obvious until someone points you in the right direction. Happy New Year.

                      Comment


                        #12
                        Re: UX header problem with iPhone Safari

                        The fact that the PanelHeader sometimes scrolls off the screen on iOS when the keyboard comes up, is not a bug in Alpha. It is unfortunately the way the Keboard is implemented by Apple.

                        The FormView control is the solution to this problem.

                        If you build your UX components using the FormView control, however, and your editors are all at the top of the screen, then when you edit a value in the form (even if the value is toward the bottom of the screen -- which would normally cause the Keyboard to scroll the screen -- thus pushing the PanelHeader out of view) the editor (which is at the top of the screen) will bring up the Keyboard, but the screen will not scroll and the PanelHeader will remain visible.

                        Comment

                        Working...
                        X