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

a_user.key.value Does not work as I was hoping

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

  • a_user.key.value Does not work as I was hoping

    I want to open the next page or go back by using the right and left arrows keys.
    On the form ONKEYEVENT.
    1 The right arrow advances but sometimes advances 2 records, (I tried to slow down the repeat and rate)
    There are no more tab positions beyond the sitting field.
    2 The left arrow moves in the form to prior tab positions and do not move the form to previous record.
    Using a button, and click works.
    Is this code wrong? Any advise?

    If a_user.key.value="{RIGHT}" Then
    a_user.key.handled=.T.
    ' If a_user.key.event = "RIGHT" Then
    parentform.fetch_next()
    If a_user.key.value="{LEFT}" Then
    a_user.key.handled=.T.
    ' If a_user.key.event = "LEFT" Then
    parentform.fetch_Prev()
    End If
    End If

  • #2
    Re: a_user.key.value Does not work as I was hoping

    You might try mapping a different key to perform the action. I use the ' * ' to do this on a form where the user is entering numeric data from the numeric keypad. Or you might try adding the Shift or Ctrl key to make it a hot key since the arrow keys already have a directional movement...
    Last edited by MoGrace; 09-14-2016, 12:35 PM.
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


    • #3
      Re: a_user.key.value Does not work as I was hoping

      Completely unclear to me why you ignored the example in the documentation.
      Code:
      If a_user.key.value="{RIGHT}" Then
      	a_user.key.handled=.T.
      	IF a_user.key.event = "down" THEN
      		parentform.fetch_next()
      	End if
      end if
      If a_user.key.value="{LEFT}" Then
      	a_user.key.handled=.T.
      	IF a_user.key.event = "down" THEN
      		parentform.fetch_Prev()
      	End If
      End If
      There can be only one.

      Comment


      • #4
        Re: a_user.key.value Does not work as I was hoping

        Thanks Robin. In this case I was trying to imitate like other apps or games.
        There are other features, using the mouse for a while, becomes uncomfortable. Also I have to keep the mouse in a certain location.
        Is minor, but I was hoping to improve it. (A while could be 1 or 2 hrs)
        The reason for using those keys is because they are accessible by hand in the keyboard and they mean the intention of backward and forward.
        According to the doc. a_user.key.handled=.T. is to make that key not function as originally intended.
        Am I wrong here?
        It seems that line has no operation at all. I was hoping that I was using it wrong and it will have proper syntax.
        As I said the -> works, but some time gives me 2 advances in stead of the expected 1.
        Could it that the pressing -> provides more that just forward or Alpha interpret it as more that one key?

        Comment


        • #5
          Re: a_user.key.value Does not work as I was hoping

          Thanks Stan, I am using the doc sample. The difference is down vs right. left vs up in both lines
          Notice commented 2nd option. I did tried the commented line and did not made any difference.
          and it would have required to add 2 end ifs.
          Am I missing something?

          Comment


          • #6
            Re: a_user.key.value Does not work as I was hoping

            Works for me.

            a_user.key.value is tested for left or right
            a_user.key.event won't ever be left or right or anything but up or down

            The reason your right event processes 2 records is likely because it fires on right arrow being pressed (down) and right arrow being released (up).
            There can be only one.

            Comment


            • #7
              Re: a_user.key.value Does not work as I was hoping

              Ah..... value -- event . That explains it, and yes IT WORKS. No extras & backward and forward.
              Thanks for the correction and the interpretation Stan.

              Comment


              • #8
                Re: a_user.key.value Does not work as I was hoping

                And for a case like space bar to move forward:
                IF a_user.key.value = ui_keycode_normalize("{chr(32)}") THEN
                a_user.key.handled = .T.
                IF a_user.key.event = "down" THEN
                parentform.fetch_next()
                END IF
                END IF

                Comment

                Working...
                X