Mercurial > hg > xemacs-beta
annotate tests/Dnd/README @ 5179:14fda1dbdb26
add memory usage info for specifiers
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-03-29 Ben Wing <ben@xemacs.org>
* alloc.c:
* alloc.c (lisp_object_storage_size):
* alloc.c (Fobject_memory_usage):
* alloc.c (lisp_object_memory_usage_full):
Don't crash if passed a non-record object (int or char).
* alloc.c (tree_memory_usage_1):
* lrecord.h:
New function tree_memory_usage() to return the memory usage of
a tree of conses and/or vectors.
* lisp.h:
* lisp.h (PRIVATE_UNVERIFIED_LIST_LOOP_7):
Add SAFE_LIST_LOOP_* functions for looping over a list not known
to be correct or non-circular, but without signalling an error --
instead, just stop enumerating when an error detected.
* emacs.c (main_1):
* specifier.c:
* specifier.c (specifier_memory_usage):
* specifier.c (vars_of_specifier):
* symsinit.h:
Add memory usage info for specifiers.
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Mon, 29 Mar 2010 22:47:55 -0500 |
| parents | bc4f2511bbea |
| children |
| rev | line source |
|---|---|
| 428 | 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 To test the code do the following: | |
| 7 1) call 'bash droptest.sh' to create the test files in /tmp | |
| 8 2) load and eval droptest.el in XEmacs | |
| 9 3) Try to do some internal DnD by using the sources and targets | |
| 10 in the new buffer | |
| 11 4) Do some external DnD: | |
|
4790
bc4f2511bbea
Remove support for the OffiX drag-and-drop protocol. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
428
diff
changeset
|
12 4a) CDE: use dtfile and dtpad |
|
bc4f2511bbea
Remove support for the OffiX drag-and-drop protocol. See xemacs-patches
Jerry James <james@xemacs.org>
parents:
428
diff
changeset
|
13 4b) MSWindows: well, explorer should do. But only file data |
| 428 | 14 should work, and I don't know if the test |
| 15 already handles this. | |
| 16 | |
| 17 The misc-user-event now also responds as a button-x-event | |
| 18 to the event-* query functions. | |
| 19 | |
| 20 The function of a drag is called dragdrop-drop-dispatch | |
| 21 as you can see in droptest.el. From within the function | |
| 22 you can access the actual misc-user-event through the | |
| 23 current-mouse-event variable. | |
| 24 | |
| 25 Short description of the object part of a drop misc-user-event: | |
| 26 ( TYPE . DATA ) | |
| 27 TYPE is either the symbol dragdrop_MIME | |
| 28 or the symbol dragdrop_URL | |
| 29 | |
| 30 DATA is a list of URL strings if TYPE is dragdrop_URL | |
| 31 if TYPE is dragdrop_MIME DATA is either a string | |
| 32 which contains the MIME data, or it is a list of | |
| 33 ( CONTENT-TYPE CONTENT-ENCODING MIME-DATA ) | |
| 34 CONTENT-TYPE is encoded for tm-view (list, first element type, | |
| 35 rest key.value conses) | |
| 36 CONTENT-ENCODING is a string | |
| 37 MIME-DATA is a string | |
| 38 | |
| 39 CONTENT-TYPE and -ENCODING can be directly supplied to mime/viewer-mode. | |
| 40 |