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

Overriding alpha hotkeys.

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

    Overriding alpha hotkeys.

    I want to use "F1" as a close on forms, but alpha's context i bound to it. Is there anyway to override this?

    -Eric

    #2
    Re: Overriding alpha hotkeys.

    If I remember correctly, Alpha calls these accelerator keys and if you assign one it will override the defaults. Try it and that should answer your question.

    Comment


      #3
      Re: Overriding alpha hotkeys.

      what if i want it on a form that doesn't have a menu attached.. is there a way besides the accelerator keys in a menu... like an onkey, or is there a system way to turn off the alpha hotkeys?

      What about a script. Can you write a script that fires in the autoexec file to turn F1 off, unless called in onkey, or push command?

      Comment


        #4
        Re: Overriding alpha hotkeys.

        Eric,
        A search would most likely bring up MANY results, among them, probably will include the few I have gathered into my help file (some repetition) that I have attached.











        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: Overriding alpha hotkeys.

          Hey Eric... You did try looking up OnKey in the help file right?

          If you do, you should find your answer. Specify a null event for the keys you want to override and you should be good. And if this is something you want on several forms, then create a function for all the onkey calls you want to make and then you just have to place that function on each form.

          HTH

          Comment


            #6
            Re: Overriding alpha hotkeys.

            Hint: I put a "Done_btn" on all my forms. In rare instances it's even a hidden button. When it isn't hidden, the text might be anything (Close, Close Window, Done, Return to Menu, etc., etc.) but the name of the button is always the same - "Done_btn".

            This allows me to do different things on different forms when the "Done_btn" is pushed but still activate it on every form with the F1 key. Also, by storing my OnKey events in one global script/function, I can just call the global script rather than re-typing it in every form. (Oops! I see Doug already mentioned using a global function.)

            My Std_OnKey event actually traps about 10-15 actions and includes this for the closing forms (assuming I used the F1 key):
            Code:
            IF a_user.key.value = "{F1}"
            	IF is_object( parentform:Done_btn.this )
            		a_user.key.handled = .T.
            		IF a_user.key.event = "down"
            			parentform:done_btn.push()
            		END IF
            	END IF
            END IF
            FWIW, I use the following keys because they don't interfer with other A5 keys:
            F10 = Enter New Record (Enter_btn)
            F11 = Find (Find_btn)
            F12 = Close the parent form (Done_btn)

            I chose the F12 key for another reason. Most people I know read from left to right so the "end" is logically on the right side and users seem to pick up on it pretty quick.

            Comment


              #7
              Re: Overriding alpha hotkeys.

              Hi Cal,
              Now I know where I got the "Key - button_push" text that I listed in my last post for possible solutions. :)
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment

              Working...
              X