Mercurial > projects > dwt2
view org.eclipse.swt.win32.win32.x86/src/org/eclipse/swt/widgets/Listener.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 | 9f32c409fe27 |
children |
line wrap: on
line source
/******************************************************************************* * Copyright (c) 2000, 2005 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.widgets.Listener; import org.eclipse.swt.widgets.Event; version(Tango){ import tango.core.Traits; import tango.core.Tuple; } else { // Phobos import std.traits; import std.typetuple; } /** * Implementers of <code>Listener</code> provide a simple * <code>handleEvent()</code> method that is used internally * by SWT to dispatch events. * <p> * After creating an instance of a class that implements this interface * it can be added to a widget using the * <code>addListener(int eventType, Listener handler)</code> method and * removed using the * <code>removeListener (int eventType, Listener handler)</code> method. * When the specified event occurs, <code>handleEvent(...)</code> will * be sent to the instance. * </p> * <p> * Classes which implement this interface are described within SWT as * providing the <em>untyped listener</em> API. Typically, widgets will * also provide a higher-level <em>typed listener</em> API, that is based * on the standard <code>java.util.EventListener</code> pattern. * </p> * <p> * Note that, since all internal SWT event dispatching is based on untyped * listeners, it is simple to build subsets of SWT for use on memory * constrained, small footprint devices, by removing the classes and * methods which implement the typed listener API. * </p> * * @see Widget#addListener * @see java.util.EventListener * @see org.eclipse.swt.events */ public interface Listener { /** * Sent when an event that the receiver has registered for occurs. * * @param event the event which occurred */ void handleEvent (Event event); } /// Helper class for the dgListener template function private class _DgListenerT(Dg,T...) : Listener { version(Tango){ alias ParameterTupleOf!(Dg) DgArgs; static assert( is(DgArgs == Tuple!(Event,T)), "Delegate args not correct: delegate args: ("~DgArgs.stringof~") vs. passed args: ("~Tuple!(Event,T).stringof~")" ); } else { // Phobos alias ParameterTypeTuple!(Dg) DgArgs; static assert( is(DgArgs == TypeTuple!(Event,T)), "Delegate args not correct: delegate args: ("~DgArgs.stringof~") vs. passed args: ("~Tuple!(Event,T).stringof~")" ); } Dg dg; T t; private this( Dg dg, T t ){ this.dg = dg; static if( T.length > 0 ){ this.t = t; } } void handleEvent( Event e ){ dg(e,t); } } /++ + dgListener creates a class implementing the Listener interface and delegating the call to + handleEvent to the users delegate. This template function will store also additional parameters. + + Examle of usage: + --- + void handleTextEvent (Event e, int inset ) { + // ... + } + text.addListener (SWT.FocusOut, dgListener( &handleTextEvent, inset )); + --- +/ Listener dgListener( Dg, T... )( Dg dg, T args ){ return new _DgListenerT!( Dg, T )( dg, args ); }