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

Check key strokes before printing on screen

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

    Check key strokes before printing on screen

    I have an Alpha Five program running but two of our machines are having an issue with the numpad where when 7 or 1 is pressed, Home and End are being sent as well as the number. It is due to they type of computer being used. Is there a way to filter the key strokes as they come in, and ignore them when Home or End is found. In a sence, what I'm trying to do is something like:
    if (A_USER.KEY.value = "{Home}" ) then
    A_USER.KEY.handled = .T.
    end if

    But alpha five does not accept this for some reason. (It doesn't break anything, just doesn't have the desired affect)
    Any thoughts?

    #2
    Re: Check key strokes before printing on screen

    I'm not clear where you are trying to use the code. Only forms have onkey events. The snippet you posted is only useful in coding the onkey event.
    There can be only one.

    Comment


      #3
      Re: Check key strokes before printing on screen

      http://www.computerhope.com/issues/ch000949.htm

      Might be worth a try on the ones causing you grief.
      See our Hybrid Option here;
      https://hybridapps.example-software.com/


      Apologies to anyone I haven't managed to upset yet.
      You are held in a queue and I will get to you soon.

      Comment


        #4
        Re: Check key strokes before printing on screen

        Yes, this is being used on a form.

        Comment


          #5
          Re: Check key strokes before printing on screen

          I used the above and put a debug in it and it works fine. What do you want it to do when it is handled? It will only keep doing what it was already doing when pressed with your script
          -----------------------------------------------
          Regards
          Mark Pearson
          [email protected]
          Youtube channel
          Website

          Comment


            #6
            Re: Check key strokes before printing on screen

            I want to block or ignore the key stroke if home or end is pressed. I thought that was what the handled = .t. was for. But I may have been mistaken. I don't wan't home/end to be passed to the application. When I was testing this script, I tried launching a message box when home was pressed to but nothing happend. The onKey didn't seeme to recogize home using this method.

            Comment


              #7
              Re: Check key strokes before printing on screen

              Try this for the onkey event for a form.


              Code:
              IF a_user.key.value = "{Home}" THEN
                  a_user.key.handled = .T.
                  IF a_user.key.event = "down" THEN
                       ui_msg_box("Key","Trapped the home key.")
                  END IF
              END IF
              There can be only one.

              Comment


                #8
                Re: Check key strokes before printing on screen

                A simple end should work

                IF a_user.key.value = "{Home}" THEN

                end
                END IF
                -----------------------------------------------
                Regards
                Mark Pearson
                [email protected]
                Youtube channel
                Website

                Comment

                Working...
                X