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

I want to make the detail view of my UX read only

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

    I want to make the detail view of my UX read only

    I want to make the detail view of my UX ready only. What is the best way to do that. I have flipped various checkboxes, and the data can still be changed. I do not want that to be a possibility at all. Any ideas would be appreciated. Thanks!

    #2
    Re: I want to make the detail view of my UX read only

    Detail View of a List Control? Read only... period? Every row... or specific rows based on something?

    Read only in the sense that changes cannot be saved? Or users cannot make any changes?

    List Detail View controls can be set Read only.

    Comment


      #3
      Re: I want to make the detail view of my UX read only

      Yes, sorry, detail view of a list control. Read only as in I don't want anyone to ever be able to change the data from this UX.

      Seems like a simple thing, but can't make it work. I went into the detail view tab, clicked on table properties, and checked "read only". But the data can still be changed from within the UX detail view. Is that the wrong place to set it to read only?

      Comment


        #4
        Re: I want to make the detail view of my UX read only

        For each of the Detail View Controls... turn on it's Readonly property. This isn't in the List or Detail View properties... but rather the properties for each control used.

        Comment


          #5
          Re: I want to make the detail view of my UX read only

          Ok, so did a little more testing. Maybe it is read only, but I don't like that it even let's you click on the data. Check out my video:



          I am able to manipulate the data. When I go back to the list, and then back to the detail view, the change is still there. If I refresh the browser, the change is gone. So it never really made the change I guess. But is there a way to set it so you can't even "temporarily" manipulate the data?

          Thanks,

          Comment


            #6
            Re: I want to make the detail view of my UX read only

            I think we're getting wrapped around the axle a bit here. I see you have the UX Controls part_detail, lens_detail etc. For each of these controls (these are the Detail View controls) change the Readonly property... check it on. This stops the user from getting into the control.

            Comment


              #7
              Re: I want to make the detail view of my UX read only

              Got it, thanks. One other question on the detail list. It seems that I can only drag the screen on certain parts of the list. Any setting change that will allow me to drag anywhere on the screen?

              Comment


                #8
                Re: I want to make the detail view of my UX read only

                The List Control is set to Fill Container. You can drag anywhere within the List Data section. Where else would you like to drag?

                Comment


                  #9
                  Re: I want to make the detail view of my UX read only

                  When I test the detail view from a mobile device, I have to touch the edge of the controls with my finger in order to drag/scroll up or down. If I don't perfectly touch the edge of a control, the screen doesn't drag/scroll. The search and list view don't seem to have this problem, just the detail view. I want to be able to touch anywhere (inside the control or whatever), and drag/scroll the screen up or down.

                  Comment


                    #10
                    Re: I want to make the detail view of my UX read only

                    I've had the same problem with my mobile app Carl. My fix was to increase the margins around the controls. It restored the ability to scroll quite a bit, although still not exactly the same feel as in other google apps I've used.

                    Comment


                      #11
                      Re: I want to make the detail view of my UX read only

                      In most cases, if you don't put your controls within a 'container' and just have them on the panel card....it will scroll as you expect. The Panel Card is a container on it's own. Of course I'm assuming you have the controls in a container and I'm assuming that you don't need a container for some other reason (which you may). On a Panel Card if controls go beyond the viewable pane it will scroll up and down as needed.

                      Comment


                        #12
                        Re: I want to make the detail view of my UX read only

                        If working with a phone and controls are are set to 100% width and in, or not in, a container, then scrolling is difficult. You must access non-control space... the space between controls or to the left or right of controls. If I can, I usually set the controls to something less than 100% and center them. This leaves me with a bit of space at the edges for scrolling.

                        Comment


                          #13
                          Re: I want to make the detail view of my UX read only

                          One other thing you could do is create a javascript function that passes in the panel, reads the controls, and then modifies the properties of the fields programmatically. Kind of a pain to do initially, but you would only have to do this once. Call the function when the panel loads.

                          Comment


                            #14
                            Re: I want to make the detail view of my UX read only

                            Hi David, what you are saying makes sense. You may want to actually use containers in that case. Another possibility is to break up the interface so that you take some sort of action to go to the other fields...and eliminate scrolling in the UX for detail editing. Of course, phones are all different sizes so that can be a challenge also.

                            Comment


                              #15
                              Re: I want to make the detail view of my UX read only

                              Yes... containers are used where appropriate. If it makes sense to split up the controls, then that's done as well. Sometimes you'd just like a panel of controls to go through and edit / update. Scrolling is a common issue. Alpha has addressed this with the use of a FormView control. The detail for a FormView is easy to scroll through... but you do lose the immediate edit / update process.

                              Comment

                              Working...
                              X