Mercurial > hg > xemacs-beta
view tests/Dnd/README @ 4881:a4322ac49e37
break out common separate-into-runs routines into redisplay-xlike-inc.c
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-01-18 Ben Wing <ben@xemacs.org>
* redisplay-xlike-inc.c:
* redisplay-xlike-inc.c (separate_textual_runs_nomule):
* redisplay-xlike-inc.c (separate_textual_runs_xft_nomule):
* redisplay-xlike-inc.c (separate_textual_runs_xft_mule):
* redisplay-xlike-inc.c (separate_textual_runs_mule):
Break separate_textual_runs_* functions from redisplay-x.c.
(Code in redisplay-gtk.c should have been identical but was
bit-rotted.)
* redisplay-gtk.c:
* redisplay-x.c:
Delete code, replace with include statement.
* depend: Regenerate.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Mon, 18 Jan 2010 06:21:05 -0600 |
parents | bc4f2511bbea |
children |
line wrap: on
line source
* Sun May 3 1998 Oliver Graf <ograf@fga.de> This path contains test code for the new XEmacs Drag'n'Drop code. To test the code do the following: 1) call 'bash droptest.sh' to create the test files in /tmp 2) load and eval droptest.el in XEmacs 3) Try to do some internal DnD by using the sources and targets in the new buffer 4) Do some external DnD: 4a) CDE: use dtfile and dtpad 4b) MSWindows: well, explorer should do. But only file data should work, and I don't know if the test already handles this. The misc-user-event now also responds as a button-x-event to the event-* query functions. The function of a drag is called dragdrop-drop-dispatch as you can see in droptest.el. From within the function you can access the actual misc-user-event through the current-mouse-event variable. Short description of the object part of a drop misc-user-event: ( TYPE . DATA ) TYPE is either the symbol dragdrop_MIME or the symbol dragdrop_URL DATA is a list of URL strings if TYPE is dragdrop_URL if TYPE is dragdrop_MIME DATA is either a string which contains the MIME data, or it is a list of ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA ) CONTENT-TYPE is encoded for tm-view (list, first element type, rest key.value conses) CONTENT-ENCODING is a string MIME-DATA is a string CONTENT-TYPE and -ENCODING can be directly supplied to mime/viewer-mode.