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

Form modal or modeless flag

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

    Form modal or modeless flag

    If a form is set to Modal is there a variable you can read to show if the user has pressed the F3 key to allow editing of the form. What I am looking for is something like:

    if form.iseditable then action1 else action2

    #2
    Re: Form modal or modeless flag

    Usually
    allow_editing() does the trick

    It sometimes, for reasons I haven't fathomed, doesn't reflect the change until you beginning an edit after F3 pressed.

    It might be that the form needs an event. Maybe one of the guru team can answer that.

    Comment


      #3
      Re: Form modal or modeless flag

      Is there some reason you don't want to use the OnKey event to trap the F3 key?

      Comment


        #4
        Re: Form modal or modeless flag

        Thanks for the suggestion Tom, I may be off track - If I may, while I have your attention
        Open this cut down version of a little app I use to collect and monitor rentals

        The top left quadrant is the the selection box

        The form will open with topparent.Mode_Get() not "VIEW" even though the form is set modal AND the form init and acivate events contain topparent.allow_change(.F.). only when trying to edit does it register mode as VIEW

        Press F3 OR click EDIT and also only when starting to edit does it register as not VIEW mode

        Theres a kind of delay thing back and forth
        Attached Files

        Comment


          #5
          Re: Form modal or modeless flag

          I took a look using v10. ( Don't have v11 on this machine). Realized I don't understand your last post. Is there a question in there somewhere?

          May I suggest you leave the "default" pane of the conditional object empty?

          Comment


            #6
            Re: Form modal or modeless flag

            Tom, the question was regarding correct appearance of the respective buttons to EDIT and those to SAVE or CANCEL.
            A.) the timing when switched by user action not switching the relevant display, and
            B.) incorrect display at startup.

            Using these conditions instead;-
            (topparent.GetActiveObjParent().restrict_change=.f.).and.(.not.allow_editing()) - for display of the button to EDIT
            and 'E'$topparent.command('?RECORD_CANCEL') to display the SAVE and CANCEL
            These conditions work correctly for part A.). Copied from the A5 toolbar.

            As far as B.) there is no more default display, so the form opens with the buttons SAVE and CANCEL event though not in EDIT mode
            Only when user changes focus does it rectify. I will try other ways than messing with the conditional display.

            BTW I am also using V10
            Thanks
            Ray

            Comment


              #7
              Re: Form modal or modeless flag

              Ray, the message board is divided into a series of separate forums. You've posted your question in the forum for A5v11 NOT A5v10.

              I'm still uncertain what your question might be. Your last post tells me what your question is about but does not, to my way of thinking, ask a question. Pardon me for being pedantic. To me questions begin with "How do I ... ? " or "Why is ... ?" or "Can I ... ?" etc.

              Anyway, here's a screencast that explains what I was trying to describe in my previous post.

              http://screencast.com/t/J4qKDxlFZaT

              It illustrates a simple way to prevent the conditional object from initially display the wrong button.

              Comment


                #8
                Re: Form modal or modeless flag

                Ja Tom
                I'm guilty on a couple of counts of disorder;
                In post two I replied to John, which you commented on and then hell broke loose
                I hijacked the post without checking the version
                Pushed my problem over to you
                all without asking a clear question.

                Once I get to view your screencast I am sure my question will be answered - that was ultimately it...
                prevent the conditional object from initially display the wrong button
                No harm no foul.

                I want to comment that there have been previous threads, without resolution, to this same problem and it could now be solved in its entirety.
                So I hope others can benefit.
                John do you have your solution?

                Thanks Tom
                Last edited by Ray in Capetown; 03-05-2012, 01:00 PM.

                Comment


                  #9
                  Re: Form modal or modeless flag

                  Tom, you showed how to remove the text and button. I put them there - to help the user on screen startup.
                  You didn't re-open the screen, its different than return after design change.

                  I have however resolved the original problem as I described post 6
                  I just need to find a way to get the screen to open correctly.

                  Comment


                    #10
                    Re: Form modal or modeless flag

                    Ray, it sounds like I don't understand what you are looking for. Maybe someone else can help you. Otherwise, please describe in detail what "get the screen to open correctly" means to you.

                    Comment


                      #11
                      Re: Form modal or modeless flag

                      Sure Tom - thanks for the opportunity. ... open the sample that you used for the screencast.
                      Upon opening, it will show no instruction (or a default), but it should reflect the current Mode (and therefore display "F3 EDIT" button).
                      Thats it.

                      It first needs a user clicking somewhere to "trigger" the condition to display relevant buttons for the current mode.
                      The users' gripe is the it is not clear to them what they are supposed to do upon opening.

                      I have changed the code to trigger the change in mode immediately thereafter when changed
                      That which you see at 2 mins in the screencast - pressed F3 button but it gave no indication.
                      With the code (post6) used for the condition, it reflects immediately. I'm not 100% sure why it wasnt with the prev version you have.
                      Last edited by Ray in Capetown; 03-06-2012, 07:19 AM.

                      Comment


                        #12
                        Re: Form modal or modeless flag

                        Maybe this will be clearer for them.

                        I've changed the properties of the conditional object and I've changed the onPUsh event for the F3 button.

                        Hopefully my changes will be clear. Holler if you have questions.

                        Comment


                          #13
                          Re: Form modal or modeless flag

                          I'm unable right now, but thanks Tom (in An...ticipation)

                          Comment


                            #14
                            Re: Form modal or modeless flag

                            Yes Tom,
                            It opens correctly. I will take a look to learn what you did to fix that and that answers my question (that I didn't properly ask in the first place).

                            It still leaves the "Press F3 EDIT" button visible after being pressed and in edit mode.
                            Only when one actually starts an edit does it correct that.
                            This I can rectify.

                            It should work then as a user would expect.

                            PS
                            I have to add that without having users wanting to use the stuff, my job would be much easier.

                            Comment


                              #15
                              Re: Form modal or modeless flag

                              Only when one actually starts an edit does it correct that.
                              Perhaps the F3 button could be suppressed once changes are allowed, but I don't think I'd want Cancel and Save buttons to appear until actual edits begin. To my way of thinkin' there's nothing to cancel or save until edits begin.

                              Comment

                              Working...
                              X