Mercurial > hg > xemacs-beta
view tests/Dnd/README @ 593:5fd7ba8b56e7
[xemacs-hg @ 2001-05-31 12:45:27 by ben]
xemacs-faq.texi: Major rewrite.
Update all MS Windows info to current.
Redo section 6.1 almost completely.
Incorporate sections 1 and 2 of Hrvoje's FAQ.
etags.el: Fix infloop when going up to the root.
s\cygwin32.h: Don't unilaterally include ntplay, but only when we're compiling
with native sound (look in configure now).
event-msw.c: Fix yet more problems with C-g handling.
Implement debug-mswindows-events.
event-stream.c, events.h, signal.c, sysdep.h:
Rearrange the signal-handling code to eliminate the former
spaghetti logic paths in it. Document clearly what
"low-level" and "high-level" timeouts are. Rename some
functions with unclear names (e.g. "...alarm...") to names
that reflect what they actually do (e.g. "...async_timeout...").
Fix numerous bugs discovered in the process.
console-x.h, event-Xt.c, event-msw.c, frame-x.c:
Hopefully make XEmacs properly maintain the "iconified"
state on frames at all times. This should fix the "can't
delete a frame with C-x 5 0 when there's another iconified
frame out there" bug.
Put a notice in of further changes that should probably
be made to clean up the frame-visibility support.
(especially directed at Jan Vroonhof)
lisp.h, miscplay.c:
Rename SBufbyte to CBufbyte to avoid a misleading name.
Eliminate UChar, which is not used anywhere and contributes
no semantic info. Add a comment about the documentation-only
properties of the char/unsigned char typedefs. Add
SChar_Binary as an explicitly `signed' version of Char_Binary
and put back the `signed' declarations in miscplay.c.
alloc.c:
Use char typedefs.
console-msw.c, device-msw.c, dialog-msw.c, editfns.c, fileio.c, glyphs-eimage.c, menubar-msw.c, ntplay.c, objects-msw.c, realpath.c, redisplay-msw.c, select-msw.c, syswindows.h, win32.c:
Eliminate numerous C++ errors.
frame-msw.c:
Eliminate numerous C++ errors and Mule-ize.
glyphs-msw.c:
Eliminate numerous C++ errors and use char typedefs.
configure.in:
Fix problems detecting both native and Linux sound on Cygwin
when compiled with --with-msw=no.
Rearrange file-coding handling a bit to avoid warning when
compiling with Mule.
configure.in, configure.usage, INSTALL:
Document XEMACS_CC and corresponding compiler option --xemacs-compiler.
Explain how to build xemacs using a C++ compiler.
author | ben |
---|---|
date | Thu, 31 May 2001 12:45:41 +0000 |
parents | 3ecd8885ac67 |
children | bc4f2511bbea |
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) OffiX: use files and editor of OffiX drag something from files or editor into XEmacs drag something from XEmacs to xv (only with OffiX patch, editor or files -- files can only move and copy within itself, cause OffiX is not quite the right thing to do) 4b) CDE: use dtfile and dtpad instead, but here everything should work. 4c) 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.