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

Function key F6

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

    Function key F6

    I have to change the function keys for our application. A handicap user can�t get Ctrl+F1 to Ctrl+10, therefore we want to use F1-F10 function keys. Has been the functions keys in our old application (Lotus Approach).

    The script within the onkey event works perfect for all function keys except F6. This function key jumps to next region of the form. It seems to be that the OnKey event will not fire.
    This is my onkey event script, what�s wrong with the function key F6. I couldn�t find any hint on this board or Alphapedia.

    Cornelius

    Code:
    dim layout_name as c = ""
    dim global vvg as n
    dim global vkom as n
    'will not fire
    debug(1)
    select
        case a_user.key.value = "{^F1}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 01a"
        case a_user.key.value = "{^F3}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 03a"
        case a_user.key.value = "{^F4}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 04a"
        case a_user.key.value = "{^F5}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 05a"
        case a_user.key.value = "{F6}" '.and. a_user.key.event = "down"
    	    debug(1)
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 06a"
        case a_user.key.value = "{^F7}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 07a"
        case a_user.key.value = "{^F8}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vvg = vg->id
    		layout_name = "Level 08a"
    	case a_user.key.value = "{^F10}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vkom = kom->id_kom
     		vvg = vg->id
    		layout_name = "Menue"
            dim lv as p
    		lv = layoutview(layout_name)
    		goto ende
    	case a_user.key.value = "{^F11}" .and. a_user.key.event = "down"
            a_user.key.handled = .T.
     		vkom = kom->id_kom
    		layout_name = "Level 11a"
            dim lv as p
    		lv = layoutview(layout_name)
    		lv.index_set("ID")
    		lv.find(vkom)
    		goto ende
    end select
    
    if layout_name <> "" then
            dim lv as p
    		lv = layoutview(layout_name)
    		lv.index_set("ID")
    		lv.find(vvg)
    
    end if
    ende:

    #2
    Re: Function key F6

    Did you mean to have

    case a_user.key.value = "{F6}"

    and not

    case a_user.key.value = "{^F6}"

    all the other keys tested are preceeded by ^.
    There can be only one.

    Comment


      #3
      Re: Function key F6

      Did you mean to have

      case a_user.key.value = "{F6}"

      and not

      case a_user.key.value = "{^F6}"

      all the other keys tested are preceeded by ^.
      Sorry yes, actually we use {^F6}, but we would like to change to {F6} and the other too (F1-F10).

      Thanks

      Cornelius

      Comment


        #4
        Re: Function key F6

        I can't trap F6 in Version 11 either. Have submitted a bug report. You may have to supply a button instead of using F6, since it's unlikely vers 10 will be patched.

        Comment


          #5
          Re: Function key F6

          Thank you for your help.

          Neither V10 nor V11 are working. V11 is just evaluation copy, because we want to update within next 2 month.
          So I tried to change US keyboard layout, but unfortunately without any success.

          At the moment we use AltGr+F6 (F1-F10), because this key combination is not so hard to get for him.

          A bug makes no sense, when they can’t reproduce the fail function.

          Cornelius

          Comment


            #6
            Re: Function key F6

            Tech support was able to reproduce the behavior and I'm advised that the fix will be in the next patch for vers 11.

            -- tom

            Comment


              #7
              Re: Function key F6

              Wow! Tom, thanks for your help. I really very glad get this news.

              I think we will buy Version 11 as quick as possible.

              Cornelius

              Comment

              Working...
              X