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

Way to assign keyboard buttons to execute actions?

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

    Way to assign keyboard buttons to execute actions?

    Hello,

    Is it possible to assign a "function" or action to certain buttons on the keyboard?

    For example, assign a function that will open a DIV when a user presses the "PAGE UP" button, or the "HOME" button?

    Thanks, Casey

    #2
    Re: Way to assign keyboard buttons to execute actions?

    Alpha Anywhere already traps certain key combinations in web components, such as ESC to cancel edits and F9 to save edits on editable components. Internally, a key watcher JavaScript method is used. While not documented, you can add your own JavaScript key watcher to web components using our built in library.

    There are some caveats with this method.

    You don't want to assign an action to a key already captured by Alpha Anywhere (such as ESC on an editable form), and once a key event is assigned to an object that is defined on a page, it fires for every component on the page. So if you assign a key watcher to a grid opened by a tabbed UI, once the grid is opened, the key watcher will fire for every component opened on the Tabbed UI. So the code run by the key needs to check for context.

    The first step is create some JavaScript in something that runs when the component or page loads. This can be in the JavaScript functions for the component, in a client side event such as 'onGridInitializeComplete' in a grid object, or directly on a page. NOTE: All of the code below is JavaScript.

    Next, attach a new key watcher to a JavaScript object. You can create a new object or use the component object. If this is placed directly on a page, you will need to define a new object.
    Code:
    var KeyWatch = new Object()
    KeyWatch.kw = new AUI.KeyWatcher([
    
    // or use the component object - grid object placeholder shown
    {Grid.object}.kw = new AUI.KeyWatcher([
    They key actions are defined in a JavaScript array in the key watcher. Each key prototype has a 'key' parameter, and a 'handle' which is the code to run if the key is pressed. A single key code array entry is something like this
    Code:
    	{key: 'F2', handle: function(){
    		// JavaScript code to run
    		alert('F2 pressed');
    		}
    	}
    Pressing the F2 key with this will show an alert. Each key array entry is separated by a comma. There is no comma after the last key definition. Once the watcher is defined, it must be turned on with
    Code:
    keyWatch.kw.on()
    
    //or if  using the component object - grid object placeholder shown
    {Grid.object}.kw.on();
    The complete JavaScript to define multiple key watchers would look something like this
    Code:
    {Grid.object}.kw = new AUI.KeyWatcher([
    	{key: 'F2', handle: function(){
    		// JavaScript code to run
    		alert('F2 pressed');
    		}
    	},
    	{key: 'SHIFT+F2', handle: function(){
    		// JavaScript code to run
    		alert('SHIFT-F2 pressed');
    		}
    	},
    	{key: 'PAGEUP', handle: function(){
    		// JavaScript code to run
    		alert('PAGEUP pressed');
    		}
    	},
    	{key: 'HOME', handle: function(){
    		// JavaScript code to run
    		alert('HOME pressed');
    		}
    	}	
    
    ]);
    {Grid.object}.kw.on();
    Key watchers support prefixes as shown above, so you can add CTRL, ALT, or SHIFT as prefixes (they can be added together). Here is a list of supported keys
    Code:
    Key = 'ENTER'
    Key = 'TAB'
    Key = 'BACKSPACE'
    Key = 'LEFT'
    Key = 'UP'
    Key = 'RIGHT'
    Key = 'DOWN'
    Key = 'ESCAPE'
    Key = 'PAGEUP'
    Key = 'PAGEDOWN'
    Key = 'END'
    Key = 'HOME'
    Key = 'INSERT'
    Key = 'DELETE'
    Key = 'F1'
    Key = 'F2'
    Key = 'F3'
    Key = 'F4'
    Key = 'F5'
    Key = 'F6'
    Key = 'F7'
    Key = 'F8'
    Key = 'F9'
    Key = 'F10'
    Key = 'F11'
    Key = 'F12'

    Comment


      #3
      Re: Way to assign keyboard buttons to execute actions?

      Now that's cool... thanks Jerry.

      Comment


        #4
        Re: Way to assign keyboard buttons to execute actions?

        Thank you Jerry so much for your response. I think this is going in the right direction, so in basic terms how would I reference my action script to run in this code?

        Sepcifically I have the code I need to run referenced as - {dialog.object}.runAction('ReturnFocusNextItem');

        By the way this is in a UX component, therefore I would replace "grid" with "dialog" correct?

        I experimented by using the following code but gave me an error (attached)Error_122415.png. Please advise how I might script it out correctly. Thanks!


        {Dialog.object}.kw = new AUI.KeyWatcher([
        {key: 'F2', handle: {dialog.object}.runAction('ReturnFocusNextItem');{
        // JavaScript code to run
        alert('F2 pressed');

        }
        }

        ]);
        {Grid.object}.kw.on();

        Comment


          #5
          Re: Way to assign keyboard buttons to execute actions?

          That's really good to know, Jerry,

          We're using this method in a UX in the onInitializeComplete event:

          Code:
          if (document.addEventListener){ 
          	document.addEventListener("keydown",keyCapt,false); //code for Moz
          }
          else {
          	document.attachEvent("onkeydown",keyCapt); //code for IE
          }
          
          
          function keyCapt(e){
          
          
            if (e.keyCode === 123) {
             		alert('F12 key');
            }
          
            // etc...
          }
          The only issue is that we have conflicts in the browser w. certain keys, such as F1 & F5.
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: Way to assign keyboard buttons to execute actions?

            Ok I see that I put my code in the wrong place, now at least I'm able to save the UX component with no errors, now when I run the following code all that happens is that I get an alert, does not run the code. Please help.

            {Dialog.object}.kw = new AUI.KeyWatcher([
            {key: 'F2', handle: function(){
            // {dialog.object}.runAction('RetreiveNextItemInfo');
            alert('F2 pressed');
            }
            }

            ]);
            {Grid.object}.kw.on();

            Comment


              #7
              Re: Way to assign keyboard buttons to execute actions?

              Even though you're assigning the KeyWatcher to the Dialog object and then turning it on for the Grid object... it does seem to work. For the sake of readability, I'd use either the Grid or Dialog object... don't mix them.

              Also, your code for the runAction is commented out. That's why you're only getting the alert.

              In my tests (Chrome and Firefox) with a UX, the function keys don't work... but HOME, PAGEUP, SHIFT-H, and others work.

              Comment

              Working...
              X