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

OnKey is "Flake" Key

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

    OnKey is "Flake" Key

    I was attempting to write a key mapping script to translate the V1 keys to V4.5, for those users used to V1.
    IE: a key press of E means new record
    C means allow edits
    F means find by key

    So I created the attached V1KEY_MAP script and then inserted the simple script_run("V1KEY_MAP") into the OnKey event of the form.

    Well my first surprise is that CTRL key combinations are not intercepted. In fact, only the actual first key pressed is detected. EG: If you want to send CTRL-E, either the CTRL or E key will be detected.

    The really big bug-a-boo (high tech term) :), is that if you press the "f", OnKey translates it as "SHIFT". I haven't bothered to test all other keys, this was upsetting enough. :(

    #2
    RE: OnKey is

    Mayhap the script has some teeny weensy (technical term) problems.

    Check the Xbasic Ref. Manual, at pg. 72. You'll see that OnKey uses the same syntax as sys_send_keys() to distinguish "E" from "Ctrl-E" from "Alt-E". Check the syntax for the sys_send_keys() function, in the same book.

    -- tom

    Comment


      #3
      RE: OnKey is

      Tom,

      Nice try buut no cigar.

      I am using the example provided by Alpha Software in the XBASIC ref. guide and it does not work.

      Besides, it does not explain what the "f" is translated as "SHIFT".

      Perhaps you might try downloading the script I attached to the original post and try it yourself?

      Comment


        #4
        RE: OnKey is

        OK, further testing shows I can trap the ALT-"somekey" if I test only for A_user.key.event = "up",
        however, CTRL combinations still appear as single key.

        BTW, does anyone know how to report bugs to Alpha Software?

        Their tech support is "pay only" unless you have an "installation" problem. Do we have to pay to report bugs now?

        Comment


          #5
          RE: OnKey is

          You missed the "curly" brackets. The following works

          sys_send_keys("{CTRL-K}")

          Jerry

          Comment


            #6
            RE: OnKey is

            Melvin, I looked at your script before posting the last. Perhaps I was mistaken, but I assumed you were trying to trap Ctrl-E instead of "E" (even though your initial message indicates otherwise). The Ctrl-E is an extended key combination, which is treated by Windows as a single keystroke, but you have to describe it correctly in your script. It did not seem to me that you were aware of the sys_send_keys() format requirement since none of your extended key combination sequences looked right. If I was mistaken, I'm sorry.

            -- tom

            Comment


              #7
              RE: OnKey is

              Tom & Jerry,

              Please read the message. The problems are
              1. CTRL key combinations cannot be >TRAPPED

              Comment


                #8
                RE: OnKey is

                Melvin,

                I beg your pardon.

                Please read the replies.

                Here's a sample illustrating how one might detect Ctrl-E, using the format for the Ctrl-E key combination discussed in connection with sys_send_keys().

                Comment


                  #9
                  RE: OnKey is

                  first, you have to have a bug, before you report it.
                  it would seem to me that trying to use sys_send_keys() in
                  an event that traps key events is asking for trouble.
                  i'm surprised that alpha five doesn't crash under those
                  circumstances.
                  anyhow, here is a simple script that will trap
                  control sequences as well as "f" and other keys:


                  if a_user.key.event="down" then
                  if a_user.key.value="{control}" then
                  ' ignore this value
                  else
                  ui_msg_box("",a_user.key.value+" was pressed")
                  end if
                  end if

                  there's an article from 1998 on www.learn alpha.com
                  that discusses how to make alpha five v 4 behave like
                  v1. you don't have to reinvent the scripts - they are all
                  there at http://www.learn alpha.com/Modeless/Modeless.htm

                  Comment


                    #10
                    RE: OnKey is

                    I'd like to especially thank Tom and Peter for their help so far. The scripts were definitely helpful in identifying the problem area.

                    As to "reinventing the wheel", if I had known the wheel existed, I would not have bothered.

                    Comment


                      #11
                      RE: OnKey is

                      Melvin, a visit to Dr. Wayne's website will pay big dividends. It's www.learn alpha.com

                      Familiarize yourself with the articles that are available there. His web site has a search engine that's useful if you don't want to print out all the Articles.

                      Dr. Wayne's xbasic book, available from Alpha Software, is a big help, too, even though it's for vers. 3. Virtually all the code examples in his book are compatible with vers. 4.

                      The search engine in this message board is a big help, too. I rely on it heavily, especially if I bump into something that feels like a bug. Before 'declaring' it to be so, I try to remember to check these resources (though sometimes I've been known to forget!)

                      And don't forget the Code Archive - a separate message board in this collection of forums (fora?) at the Alpha Software support site.

                      -- tom

                      -- tom

                      Comment


                        #12
                        RE: OnKey is

                        Tom,

                        Been there, done that! Thanks.

                        BTW, after a long time of contributing to the V1 message board, it has finally paid off for me.

                        Comment

                        Working...
                        X