|
282
|
1 * Sun May 3 1998 Oliver Graf <ograf@fga.de>
|
|
|
2
|
|
|
3 This path contains test code for the new XEmacs
|
|
|
4 Drag'n'Drop code.
|
|
|
5
|
|
|
6 Currently only drags are of interest. The internal
|
|
|
7 functions only work for OffiX. MSWindows and CDE
|
|
|
8 are broken with this patch.
|
|
|
9
|
|
|
10 The OffiX functions in mouse.el also work no longer,
|
|
|
11 because drags are now misc-user-events.
|
|
|
12
|
|
|
13 The misc-user-event now also responds as a button-x-event
|
|
|
14 to the event-* query functions.
|
|
|
15
|
|
|
16 The function of a drag is called dragdrop-drop-dispatch
|
|
|
17 as you can see in droptest.el. From within the function
|
|
|
18 you can access the actual misc-user-event through the
|
|
|
19 current-mouse-event variable.
|
|
|
20
|
|
|
21 dragtest.el works theoretically, but it needs to be
|
|
|
22 adapted to some new scheme fitting the drop code.
|
|
|
23
|
|
|
24 Short description of the object part of a drop misc-user-event:
|
|
|
25 ( TYPE . DATA )
|
|
|
26 TYPE is either the symbol dragdrop_MIME
|
|
|
27 or the symbol dragdrop_URL
|
|
|
28
|
|
|
29 DATA is a list of URL strings if TYPE is dragdrop_URL
|
|
|
30 if TYPE is dragdrop_MIME DATA is either a string
|
|
|
31 which contains the MIME data, or it is a list of
|
|
|
32 ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA )
|
|
|
33
|
|
|
34 For DATA I am thinking of some different scheme:
|
|
|
35 perhaps it would be more efficient to split the
|
|
|
36 MIME data into header and body, make a plist from
|
|
|
37 the header (for easy access), pre-convert the body
|
|
|
38 to 8bit, and also attach the original data.
|
|
|
39 This would make the access easier, but it would
|
|
|
40 require that I do a lot of MIME stuff in C, a thing
|
|
|
41 that tm-mime-view already does for us.
|
