Categories:
Audio (13)
Biotech (29)
Bytecode (36)
Database (77)
Framework (7)
Game (7)
General (507)
Graphics (53)
I/O (35)
IDE (2)
JAR Tools (101)
JavaBeans (21)
JDBC (121)
JDK (426)
JSP (20)
Logging (108)
Mail (58)
Messaging (8)
Network (84)
PDF (97)
Report (7)
Scripting (84)
Security (32)
Server (121)
Servlet (26)
SOAP (24)
Testing (54)
Web (15)
XML (309)
Collections:
Other Resources:
JDK 11 java.desktop.jmod - Desktop Module
JDK 11 java.desktop.jmod is the JMOD file for JDK 11 Desktop module.
JDK 11 Desktop module compiled class files are stored in \fyicenter\jdk-11.0.1\jmods\java.desktop.jmod.
JDK 11 Desktop module compiled class files are also linked and stored in the \fyicenter\jdk-11.0.1\lib\modules JImage file.
JDK 11 Desktop module source code files are stored in \fyicenter\jdk-11.0.1\lib\src.zip\java.desktop.
You can click and view the content of each source code file in the list below.
✍: FYIcenter
⏎ java/awt/KeyEventPostProcessor.java
/* * Copyright (c) 2001, 2013, Oracle and/or its affiliates. All rights reserved. * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. * * * * * * * * * * * * * * * * * * * * */ package java.awt; import java.awt.event.KeyEvent; /** * A KeyEventPostProcessor cooperates with the current KeyboardFocusManager * in the final resolution of all unconsumed KeyEvents. KeyEventPostProcessors * registered with the current KeyboardFocusManager will receive KeyEvents * after the KeyEvents have been dispatched to and handled by their targets. * KeyEvents that would have been otherwise discarded because no Component in * the application currently owns the focus will also be forwarded to * registered KeyEventPostProcessors. This will allow applications to implement * features that require global KeyEvent post-handling, such as menu shortcuts. * <p> * Note that the KeyboardFocusManager itself implements KeyEventPostProcessor. * By default, the current KeyboardFocusManager will be the final * KeyEventPostProcessor in the chain. The current KeyboardFocusManager cannot * be completely deregistered as a KeyEventPostProcessor. However, if a * KeyEventPostProcessor reports that no further post-processing of the * KeyEvent should take place, the AWT will consider the event fully handled * and will take no additional action with regard to the event. (While it is * possible for client code to register the current KeyboardFocusManager as * a KeyEventPostProcessor one or more times, this is usually unnecessary and * not recommended.) * * @author David Mendenhall * * @see KeyboardFocusManager#addKeyEventPostProcessor * @see KeyboardFocusManager#removeKeyEventPostProcessor * @since 1.4 */ @FunctionalInterface public interface KeyEventPostProcessor { /** * This method is called by the current KeyboardFocusManager, requesting * that this KeyEventPostProcessor perform any necessary post-processing * which should be part of the KeyEvent's final resolution. At the time * this method is invoked, typically the KeyEvent has already been * dispatched to and handled by its target. However, if no Component in * the application currently owns the focus, then the KeyEvent has not * been dispatched to any Component. Typically, KeyEvent post-processing * will be used to implement features which require global KeyEvent * post-handling, such as menu shortcuts. Note that if a * KeyEventPostProcessor wishes to dispatch the KeyEvent, it must use * {@code redispatchEvent} to prevent the AWT from recursively * requesting that this KeyEventPostProcessor perform post-processing * of the event again. * <p> * If an implementation of this method returns {@code false}, then the * KeyEvent is passed to the next KeyEventPostProcessor in the chain, * ending with the current KeyboardFocusManager. If an implementation * returns {@code true}, the KeyEvent is assumed to have been fully * handled (although this need not be the case), and the AWT will take no * further action with regard to the KeyEvent. If an implementation * consumes the KeyEvent but returns {@code false}, the consumed * event will still be passed to the next KeyEventPostProcessor in the * chain. It is important for developers to check whether the KeyEvent has * been consumed before performing any post-processing of the KeyEvent. By * default, the current KeyboardFocusManager will perform no post- * processing in response to a consumed KeyEvent. * * @param e the KeyEvent to post-process * @return {@code true} if the AWT should take no further action with * regard to the KeyEvent; {@code false} otherwise * @see KeyboardFocusManager#redispatchEvent */ boolean postProcessKeyEvent(KeyEvent e); }
⏎ java/awt/KeyEventPostProcessor.java
Or download all of them as a single archive file:
File name: java.desktop-11.0.1-src.zip File size: 7974380 bytes Release date: 2018-11-04 Download
⇒ JDK 11 java.instrument.jmod - Instrument Module
2022-08-06, 194051👍, 5💬
Popular Posts:
maven-core-3.5.4.jar is the JAR file for Apache Maven 3.5.4 Core module. Apache Maven is a software ...
MXP1 is a stable XmlPull parsing engine that is based on ideas from XPP and in particular XPP2 but c...
JDK 11 java.rmi.jmod is the JMOD file for JDK 11 RMI (Remote Method Invocation) module. JDK 11 RMI m...
JDK 11 java.management.jmod is the JMOD file for JDK 11 Management module. JDK 11 Management module ...
JSP(tm) Standard Tag Library 1.0 implementation - Jakarta Taglibs hosts the Standard Taglib 1.0, an ...