Keystroke Handling"

From Documentation
m
 
(14 intermediate revisions by 3 users not shown)
Line 7: Line 7:
 
=ENTER and ESC=
 
=ENTER and ESC=
  
To handle ENTER key pressing, you can to listen to the event:
+
To handle ENTER key pressing, you can listen to the event:
 
* '''onOK''' (notice O and K are both in upper case).  
 
* '''onOK''' (notice O and K are both in upper case).  
  
To handle ESC key pressing, you can to listen to the event:
+
To handle ESC key pressing, you can listen to the event:
 
* '''onCancel'''  
 
* '''onCancel'''  
  
 
For example:
 
For example:
  
<source lang="xml" high='10, 11'>
+
<source lang="xml" highlight='10, 11'>
 
     <grid id="form" apply="org.zkoss.reference.developer.uipattern.KeystrokeComposer">
 
     <grid id="form" apply="org.zkoss.reference.developer.uipattern.KeystrokeComposer">
 
         <rows>
 
         <rows>
Line 35: Line 35:
  
  
<source lang="java" high='15, 21'>
+
<source lang="java" highlight='15, 21'>
 
package org.zkoss.reference.developer.uipattern;
 
package org.zkoss.reference.developer.uipattern;
  
Line 65: Line 65:
  
  
Notice that the <tt>onOK</tt> and <tt>onCancel</tt> events are sent to the nearest ancestor of the component that has the focus. In other words, if you press ENTER in a textbox, then ZK will look up the textbox, its parent, its parent's parent and so on to see if any of them has been registered a listener for <tt>onOK</tt>. If found, the event is sent to it. If not found, nothing will happen.
+
Notice that the <code>onOK</code> and <code>onCancel</code> events are sent to the nearest ancestor of the component that has the focus. In other words, if you press ENTER in a textbox, then ZK will look up the textbox, its parent, its parent's parent and so on to see if any of them has been registered as a listener for <code>onOK</code>. If found, the event is sent to it. If not found, nothing will happen.
  
Also notice that, if a button gains the focus, ENTER will be intercepted by the browser and interpreted as pressed. For example, if you move the focus to the Reset button and press ENTER, you will receive <tt>onCancel</tt> rather than <tt>onOK</tt> (since <tt>onClick</tt> will be fired and it is converted to <tt>onCancel</tt> because of [[ZUML Reference/ZUML/Attributes/forward|the forward attribute]] specified).
+
Also notice that, if a button gains the focus, ENTER will be intercepted by the browser and interpreted as pressed. For example, if you move the focus to the Reset button and press ENTER, you will receive <code>onCancel</code> rather than <code>onOK</code> (since <code>onClick</code> will be fired and it is converted to <code>onCancel</code> because of [[ZUML Reference/ZUML/Attributes/forward|the forward attribute]] specified).
  
 
=Control Keys=
 
=Control Keys=
  
To handle the control keys, you have to specify the keystrokes you want to handle with <javadoc method="setCtrlKeys(java.lang.String)">org.zkoss.zul.impl.XulElement</javadoc>. Then, if any child component gains the focus and the user presses a keystroke matches the combination, the <tt>onCtrlKey</tt> will be sent to the component with an instance of <javadoc>org.zkoss.zk.ui.event.KeyEvent</javadoc>.
+
To handle the control keys, you have to specify the keystrokes you want to handle with <javadoc method="setCtrlKeys(java.lang.String)">org.zkoss.zul.impl.XulElement</javadoc>. Then, if any child component gains the focus and the user presses a keystroke that matches the combination, the <code>onCtrlKey</code> will be sent to the component with an instance of <javadoc>org.zkoss.zk.ui.event.KeyEvent</javadoc>.
  
Like ENTER and ESC, you could specify the listener and the <tt>ctrlKeys</tt> property in one of the ancestors. ZK will search the component having the focus, its parent, its parent's parent and so on to find if any of them specifies the <tt>ctrlKeys</tt> property that matches the keystroke.
+
Like ENTER and ESC, you could specify the listener and the <code>ctrlKeys</code> property in one of the ancestors. ZK will search the component having the focus, its parent, its parent's parent and so on to find if any of them specifies the <code>ctrlKeys</code> property that matches the keystroke.
  
 
For example,
 
For example,
Line 88: Line 88:
 
== Allowed Control Keys ==
 
== Allowed Control Keys ==
  
{|  border="1" | width="100%"
+
{|  class="wikitable" | width="100%"
 
!  <center>Key</center>
 
!  <center>Key</center>
 
! <center>Syntax</center>
 
! <center>Syntax</center>
Line 96: Line 96:
 
| Control
 
| Control
 
| <center>^[?]</center>
 
| <center>^[?]</center>
| <tt>[?]</tt> can be '''a~z, 0~9, #[?]''',  
+
| <code>[?]</code> can be '''a~z, 0~9, #[?]''',  
e.g. <tt>^k</tt> represents <tt>Ctrl+k</tt>  
+
e.g. <code>^k</code> represents <code>Ctrl+k</code>  
  
 
|-  
 
|-  
 
| Alt  
 
| Alt  
 
| <center>@[?]</center>
 
| <center>@[?]</center>
| <tt>[?]</tt> can be '''a~z, 0~9, #[?]''',
+
| <code>[?]</code> can be '''a~z, 0~9, #[?]''',
e.g. <tt>@k</tt> represents <tt>Alt+k</tt>
+
e.g. <code>@k</code> represents <code>Alt+k</code>
  
 
|-
 
|-
 
| Shift
 
| Shift
 
| <center>$[?]</center>
 
| <center>$[?]</center>
| <tt>[?]</tt> can be '''#[?]'''. Note: $a ~ $z are not supported.
+
| <code>[?]</code> can be '''#[?]'''. Note: $a ~ $z are not supported.
e.g. <tt>$#down</tt> represents <tt>Shift+↓</tt>
+
e.g. <code>$#down</code> represents <code>Shift+↓</code>
  
 
|-
 
|-
 
| Mac command(⌘)
 
| Mac command(⌘)
 
| <center>%[?]</center>
 
| <center>%[?]</center>
| <pre>since 8.5</pre>
+
|  
<tt>[?]</tt> can be ''' a~z, 0~9, #[?]'''.
+
{{versionSince| 8.5.0}}
e.g. <tt>%k</tt> represents <tt>command+k</tt>
+
<code>[?]</code> can be ''' a~z, 0~9, #[?]'''.
 +
e.g. <code>%k</code> represents <code>command+k</code>
 
|-
 
|-
 
| '''Navigation key'''
 
| '''Navigation key'''
 
| <center>#[?]</center>
 
| <center>#[?]</center>
| the supported value of <tt>[?]</tt> are listed below:
+
| the supported value of <code>[?]</code> are listed below:
 
|-
 
|-
 
| Home
 
| Home
Line 172: Line 173:
 
| Tab
 
| Tab
 
| <center>#tab</center>
 
| <center>#tab</center>
| Since 9.5.1
+
|
 +
{{versionSince| 9.5.1}}
 +
|-
 +
| Space
 +
| <center>#space</center>
 +
|
 +
{{versionSince| 10.0.0}}
 
|}
 
|}
  
 
=Document-level Keystrokes=
 
=Document-level Keystrokes=
  
[5.0.6]
+
{{versionSince| 5.0.6}}
  
When you set the library property [https://www.zkoss.org/wiki/ZK_Configuration_Reference/zk.xml/The_Library_Properties/org.zkoss.zk.ui.invokeFirstRootForAfterKeyDown.enabled org.zkoss.zk.ui.invokeFirstRootForAfterKeyDown.enabled] to true. If there is no widget gaining a focus when an end user presses a keystroke, ZK can forward a key event to the first root component.  
+
If you set the library property [https://www.zkoss.org/wiki/ZK_Configuration_Reference/zk.xml/The_Library_Properties/org.zkoss.zk.ui.invokeFirstRootForAfterKeyDown.enabled org.zkoss.zk.ui.invokeFirstRootForAfterKeyDown.enabled] to <code>true</code> and there is no widget gaining a focus when an end-user presses a keystroke, ZK will fire a key event to '''the first root component that has an onCtrlKey listener'''.  
For example, when visiting the following page, the <mp>div</mp> component will receive the <mp>onOK</mp> event.
+
For example, when visiting the following page, the <code>div</code> component will receive the <code>onOK</code> event.
  
 
<source lang="xml">
 
<source lang="xml">
Line 193: Line 200:
 
</source>
 
</source>
  
In other words, <code>doSomething()</code> will be called if the user presses ENTER, even though no widget ever gains the focus.
+
In other words, <code>doSomething()</code> will be called if a user presses ENTER, even though no widget ever gains the focus.
  
 
=Nested Components=
 
=Nested Components=
Line 208: Line 215:
 
</source>
 
</source>
  
Then, <code>doSecond()</code> is called if <tt>t2</tt> is the current focus, and <code>doFirst()</code> is called if <tt>t1</tt> has the focus.
+
Then, <code>doSecond()</code> is called if <code>t2</code> is the current focus, and <code>doFirst()</code> is called if <code>t1</code> has the focus.
  
 
=Key handling and onChange event=
 
=Key handling and onChange event=
When a onChange listener alone is registered on a component, onChange will be triggered by blur events exclusively.
+
When an onChange listener alone is registered on a component, onChange will be triggered by blur events exclusively.
  
 
However, some key events will cause a check for change value and will fire a change event if necessary.
 
However, some key events will cause a check for change value and will fire a change event if necessary.
  
These key events are: onOK onCancel onCtrlkeys. If a listener for any of these events is registered and triggers, an onChange event calculation will be triggered, and an onChange event will be fired if the value of the control have changed.
+
These key events are: onOK, onCancel, and onCtrlkeys. If a listener for any of these events is registered and triggered, an onChange event calculation will be triggered, and an onChange event will be fired if the value of the control has changed.
  
 
=Version History=
 
=Version History=
{{LastUpdated}}
+
 
{| border='1px' | width="100%"
+
{| class='wikitable' | width="100%"
 
! Version !! Date !! Content
 
! Version !! Date !! Content
 
|-
 
|-
Line 227: Line 234:
 
|-
 
|-
 
| 9.5.1
 
| 9.5.1
|  
+
| November 2020
 
| Add Tab key support
 
| Add Tab key support
 +
|-
 +
| 10.0.0
 +
| December 2023
 +
| Add Space key support
 
|}
 
|}
  
 
{{ZKDevelopersReferencePageFooter}}
 
{{ZKDevelopersReferencePageFooter}}

Latest revision as of 09:17, 30 January 2024


Keystroke Handling


Keystroke handling is generic. Any component inherited from XulElement can handle the key event in the same way.

ENTER and ESC

To handle ENTER key pressing, you can listen to the event:

  • onOK (notice O and K are both in upper case).

To handle ESC key pressing, you can listen to the event:

  • onCancel

For example:

    <grid id="form" apply="org.zkoss.reference.developer.uipattern.KeystrokeComposer">
        <rows>
            <row>Username:
                <textbox id="username"/>
            </row>
            <row>Password:
                <textbox id="password" type="password"/>
            </row>
            <row>
                <button label="Login" forward="form.onOK"/>
                <button label="Reset" forward="form.onCancel"/>
            </row>
        </rows>
    </grid>

Then, you could implement a composer as follows.


package org.zkoss.reference.developer.uipattern;

import org.zkoss.zk.ui.Component;
import org.zkoss.zk.ui.select.SelectorComposer;
import org.zkoss.zk.ui.select.annotation.*;
import org.zkoss.zul.Textbox;

public class KeystrokeComposer extends SelectorComposer<Component> {

    @Wire
    private Textbox username;
    @Wire
    private Textbox password;

    @Listen("onOK = #form")
    public void onOK() {
        //handle login
        System.out.println("ok");
    }

    @Listen("onCancel = #form")
    public void onCancel() {
        username.setValue("");
        password.setValue("");
    }
}


Notice that the onOK and onCancel events are sent to the nearest ancestor of the component that has the focus. In other words, if you press ENTER in a textbox, then ZK will look up the textbox, its parent, its parent's parent and so on to see if any of them has been registered as a listener for onOK. If found, the event is sent to it. If not found, nothing will happen.

Also notice that, if a button gains the focus, ENTER will be intercepted by the browser and interpreted as pressed. For example, if you move the focus to the Reset button and press ENTER, you will receive onCancel rather than onOK (since onClick will be fired and it is converted to onCancel because of the forward attribute specified).

Control Keys

To handle the control keys, you have to specify the keystrokes you want to handle with XulElement.setCtrlKeys(String). Then, if any child component gains the focus and the user presses a keystroke that matches the combination, the onCtrlKey will be sent to the component with an instance of KeyEvent.

Like ENTER and ESC, you could specify the listener and the ctrlKeys property in one of the ancestors. ZK will search the component having the focus, its parent, its parent's parent and so on to find if any of them specifies the ctrlKeys property that matches the keystroke.

For example,

<vbox ctrlKeys="@c^a#f10^#f3" onCtrlKey="doSomething(event.getKeyCode())">
    <textbox/>
    <datebox/>
</vbox>

As shown, you could use KeyEvent.getKeyCode() to know which key was pressed.

Allowed Control Keys

Key
Syntax
Description
Control
^[?]
[?] can be a~z, 0~9, #[?],

e.g. ^k represents Ctrl+k

Alt
@[?]
[?] can be a~z, 0~9, #[?],

e.g. @k represents Alt+k

Shift
$[?]
[?] can be #[?]. Note: $a ~ $z are not supported.

e.g. $#down represents Shift+↓

Mac command(⌘)
%[?]

Since 8.5.0 [?] can be a~z, 0~9, #[?]. e.g. %k represents command+k

Navigation key
#[?]
the supported value of [?] are listed below:
Home
#home
End
#end
Insert
#ins
Delete
#del
#left
#right
#up
#down
PgUp
#pgup
PgDn
#pgdn
Backspace
#bak
function key (F1, F2,... F12)
#f1, #f2, ... #f12
Tab
#tab

Since 9.5.1

Space
#space

Since 10.0.0

Document-level Keystrokes

Since 5.0.6

If you set the library property org.zkoss.zk.ui.invokeFirstRootForAfterKeyDown.enabled to true and there is no widget gaining a focus when an end-user presses a keystroke, ZK will fire a key event to the first root component that has an onCtrlKey listener. For example, when visiting the following page, the div component will receive the onOK event.

<div onOK="doSomething(event)" ctrlKeys="^K" onCtrlKey="doSomething(event)" >
press enter key or ctrl+k.
<zscript><![CDATA[
public void doSomething(KeyEvent e){
	Clients.showNotification(e.getKeyCode()+"");
}
]]></zscript>
</div>

In other words, doSomething() will be called if a user presses ENTER, even though no widget ever gains the focus.

Nested Components

Keystrokes are propagated up from the widget gaining the focus to the first ancestor widget that handles the keystroke. For example,

<div onOK="doFirst()">
   <textbox id="t1"/>
   <div onOK="doSecond()">
       <textbox id="t2"/>
   </div>
</div>

Then, doSecond() is called if t2 is the current focus, and doFirst() is called if t1 has the focus.

Key handling and onChange event

When an onChange listener alone is registered on a component, onChange will be triggered by blur events exclusively.

However, some key events will cause a check for change value and will fire a change event if necessary.

These key events are: onOK, onCancel, and onCtrlkeys. If a listener for any of these events is registered and triggered, an onChange event calculation will be triggered, and an onChange event will be fired if the value of the control has changed.

Version History

Version Date Content
5.0.6 January 2011 Document-level keystroke handling was introduced.
9.5.1 November 2020 Add Tab key support
10.0.0 December 2023 Add Space key support



Last Update : 2024/01/30

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.