Mercurial > projects > dwt2
view org.eclipse.swt.gtk.linux.x86/src/org/eclipse/swt/accessibility/AccessibleListener.d @ 120:536e43f63c81
Comprehensive update for Win32/Linux32 dmd-2.053/dmd-1.068+Tango-r5661
===D2===
* added [Try]Immutable/Const/Shared templates to work with differenses in D1/D2 instead of version statements
used these templates to work with strict type storage rules of dmd-2.053
* com.ibm.icu now also compilable with D2, but not tested yet
* small fixes
Snippet288 - shared data is in TLS
===Phobos===
* fixed critical bugs in Phobos implemention
completely incorrect segfault prone fromStringz (Linux's port ruthless killer)
terrible, incorrect StringBuffer realization (StyledText killer)
* fixed small bugs as well
Snippet72 - misprint in the snippet
* implemented missed functionality for Phobos
ByteArrayOutputStream implemented (image loading available)
formatting correctly works for all DWT's cases
As a result, folowing snippets now works with Phobos (Snippet### - what is fixed):
Snippet24, 42, 111, 115, 130, 235, 276 - bad string formatting
Snippet48, 282 - crash on image loading
Snippet163, 189, 211, 213, 217, 218, 222 - crash on copy/cut in StyledText
Snippet244 - hang-up
===Tango===
* few changes for the latest Tango trunc-r5661
* few small performance improvments
===General===
* implMissing-s for only one version changed to implMissingInTango/InPhobos
* incorrect calls to Format in toString-s fixed
* fixed loading \uXXXX characters in ResourceBundle
* added good UTF-8 support for StyledText, TextLayout (Win32) and friends
UTF functions revised and tested. It is now in java.nonstandard.*Utf modules
StyledText and TextLayout (Win32) modules revised for UTF-8 support
* removed small diferences in most identical files in *.swt.* folders
*.swt.internal.image, *.swt.events and *.swt.custom are identical in Win32/Linux32
now 179 of 576 (~31%) files in *.swt.* folders are fully identical
* Win32: snippets now have right subsystem, pretty icons and native system style controls
* small fixes in snippets
Snippet44 - it's not Snippet44
Snippet212 - functions work with different images and offsets arrays
Win32: Snippet282 - crash on close if the button has an image
Snippet293 - setGrayed is commented
and others
Win32: As a result, folowing snippets now works
Snippet68 - color doesn't change
Snippet163, 189, 211, 213, 217, 218, 222 - UTF-8 issues (see above)
Snippet193 - no tabel headers
author | Denis Shelomovskij <verylonglogin.reg@gmail.com> |
---|---|
date | Sat, 09 Jul 2011 15:50:20 +0300 |
parents | f713da8bc051 |
children |
line wrap: on
line source
/******************************************************************************* * Copyright (c) 2000, 2003 IBM Corporation and others. * All rights reserved. This program and the accompanying materials * are made available under the terms of the Eclipse Public License v1.0 * which accompanies this distribution, and is available at * http://www.eclipse.org/legal/epl-v10.html * * Contributors: * IBM Corporation - initial API and implementation * Port to the D programming language: * Frank Benoit <benoit@tionex.de> *******************************************************************************/ module org.eclipse.swt.accessibility.AccessibleListener; import org.eclipse.swt.internal.SWTEventListener; import org.eclipse.swt.accessibility.AccessibleEvent; /** * Classes that implement this interface provide methods * that deal with the events that are generated when an * accessibility client sends a message to a control. * <p> * After creating an instance of a class that implements * this interface it can be added to a control using the * <code>addAccessibleListener</code> method and removed * using the <code>removeAccessibleListener</code> method. * When a client requests information, the appropriate method * will be invoked. * </p><p> * Note: Accessibility clients use child identifiers to specify * whether they want information about a control or one of its children. * Child identifiers are increasing integers beginning with 0. * The identifier CHILDID_SELF represents the control itself. * </p> * * @see AccessibleAdapter * @see AccessibleEvent * * @since 2.0 */ public interface AccessibleListener : SWTEventListener { /** * Sent when an accessibility client requests the name * of the control, or the name of a child of the control. * <p> * Return the name of the control or specified child in the * <code>result</code> field of the event object. Returning * an empty string tells the client that the control or child * does not have a name, and returning null tells the client * to use the platform name. * </p> * * @param e an event object containing the following fields:<ul> * <li>childID [IN] - an identifier specifying the control or one of its children</li> * <li>result [OUT] - the requested name string, or null</li> * </ul> */ public void getName(AccessibleEvent e); /** * Sent when an accessibility client requests the help string * of the control, or the help string of a child of the control. * <p> * The information in this property should be similar to the help * provided by toolTipText. It describes what the control or child * does or how to use it, as opposed to getDescription, which * describes appearance. * </p><p> * Return the help string of the control or specified child in * the <code>result</code> field of the event object. Returning * an empty string tells the client that the control or child * does not have a help string, and returning null tells the * client to use the platform help string. * </p> * * @param e an event object containing the following fields:<ul> * <li>childID [IN] - an identifier specifying the control or one of its children</li> * <li>result [OUT] - the requested help string, or null</li> * </ul> */ public void getHelp(AccessibleEvent e); /** * Sent when an accessibility client requests the keyboard shortcut * of the control, or the keyboard shortcut of a child of the control. * <p> * A keyboard shortcut can either be a mnemonic, or an accelerator. * As a general rule, if the control or child can receive keyboard focus, * then you should expose its mnemonic, and if it cannot receive keyboard * focus, then you should expose its accelerator. * </p><p> * Return the keyboard shortcut string of the control or specified child * in the <code>result</code> field of the event object. Returning an * empty string tells the client that the control or child does not * have a keyboard shortcut string, and returning null tells the client * to use the platform keyboard shortcut string. * </p> * * @param e an event object containing the following fields:<ul> * <li>childID [IN] - an identifier specifying the control or one of its children</li> * <li>result [OUT] - the requested keyboard shortcut string (example: "ALT+N"), or null</li> * </ul> */ public void getKeyboardShortcut(AccessibleEvent e); /** * Sent when an accessibility client requests a description * of the control, or a description of a child of the control. * <p> * This is a textual description of the control or child's visual * appearance, which is typically only necessary if it cannot be * determined from other properties such as role. * </p><p> * Return the description of the control or specified child in * the <code>result</code> field of the event object. Returning * an empty string tells the client that the control or child * does not have a description, and returning null tells the * client to use the platform description. * </p> * * @param e an event object containing the following fields:<ul> * <li>childID [IN] - an identifier specifying the control or one of its children</li> * <li>result [OUT] - the requested description string, or null</li> * </ul> */ public void getDescription(AccessibleEvent e); }