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

sys_down_key not understanding

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

    sys_down_key not understanding

    Hi there,

    Am trying to get the following code to work

    dim hlt_key as l 'halt emails key
    dim countr as n

    hlt_key = .f. 'init

    while hlt_key = .f.
    hlt_key = sys_key_down("ENTER") 'BREAK
    countr = countr + 1
    end while

    ui_msg_box("Script Test","Counter = " + countr)

    I understand that if I hold down ENTER key hlt_key should TRUE

    What do I need to do to alter hlt_key to TRUE ??

    Looking forward
    Dave Mac

    It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

    #2
    Re: sys_down_key not understanding

    Dave,
    Try an if-then statement instead of a while-end while.
    Only way I could test it in the interactive window and works.
    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


      #3
      Re: sys_down_key not understanding

      Hi Mike,

      Thanks for your response.

      Sorry to be a pain, but I cannot get my Hlt_key True. I'm using the following code

      'Date Created: 16-May-2009 01:45:13 PM
      'Last Updated: 18-May-2009 10:06:05 AM
      'Created By : Administrator
      'Updated By : Administrator

      dim hlt_key as l 'halt emails key
      dim countr as n

      debug(1)

      hlt_key = .f. 'init

      Lab1:

      if hlt_key = .t. then
      goto finish '----->>>>>
      else
      ' hlt_key = sys_key_down("ENTER") 'BREAK
      ' hlt_key = sys_key_down("ESC") 'BREAK
      hlt_key = sys_key_down("F1") 'BREAK

      countr = countr + 1
      goto Lab1 '----->>>>>
      end if
      '
      '---------------------
      '
      Finish:

      ui_msg_box("Script Test","Counter = " + countr)

      Any Ideas ?
      Dave Mac

      It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

      Comment


        #4
        Re: sys_down_key not understanding

        Dave, I have zero experience with the function you're using. Is there a reason you aren't using an OnKey event script in your form to trap these keystrokes?

        Comment


          #5
          Re: sys_down_key not understanding

          Dave,
          Same question here as Tom. An OnKey event with a script similar to below works and is used quite often by many here. I have a feeling that for the sys_key_down() function to work you have to be holding the key down all the while the script is running to trigger the .T. you want.

          Code:
          'OnKey Events on Forms
          'Handling Key Events
          'The general approach to intercepting and handling keystrokes in your 'application is as follows.
          
          IF a_user.key.value = "{<Key_to_be_trapped>}" THEN
              a_user.key.handled = .T.
              IF a_user.key.event = "down" THEN
          
                   <Action_to_be_taken> 
          
              END IF 
          END IF
          '===============================================
          
          IF a_user.key.value = "{^d}" .OR. a_user.key.value = "{Delete}" .OR. a_user.key.value = "{Backspace}" THEN
              a_user.key.handled = .T.
              IF a_user.key.event = "down" THEN
          
                   msgbox("Key value handled")
          
              END IF 
          END IF
          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


            #6
            Re: sys_down_key not understanding

            Hi there Mike, Tom

            Thanks for the support. Without it I would have died long ago !

            I used OnKey suggestion and it works on a Form Acc_Sel_Fst_Lst as a test (which I am posting separately on the Message board, because I have an issue trying to load variables on Form Acc_Sel_Fst_Lst).

            However, I cannot get it working on my Program ? Haven't a clue why. I attach the code and resulting error.

            Any ideas ?

            Thanks
            Dave Mac

            It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

            Comment


              #7
              Re: sys_down_key not understanding

              Dave,
              I do not see an event that you have attached the code to....it needs to be placed in the OnKey event of the form.
              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


                #8
                Re: sys_down_key not understanding

                Hi Mike,

                Oops. Thanks for your quick response. This response is from the "Was my face red" department

                Thanks
                Dave Mac

                It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

                Comment

                Working...
                X