May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Oliver Graf

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > Another possible is to add the button, mod and pos info into the > > object list. dragdrop-drop-dispatch could then create a dummy > > button-xy event with the actual values (channel must also be stored > > in object) so the function can use the internal functions > > event-point (and others) to get the position in the buffer and the > > action the user wanted. > > I don't understand this. I think I have a solution. Do you think that this is evil: - when I create the misc-user-event object (the dnd-data), I cons a reverence to the event itself into it. So the function still has access to it's event. And this is how it looks... events.h defines misc_user_data as: struct misc_user_data { Lisp_Object function; Lisp_Object object; int button; unsigned char modifiers; int x, y; }; event-Xt does the following when a drop occurs (it's a nice reference loop...): XSETEVENT (lisp_event, emacs_event); emacs_event->event.eval.function = Qdragdrop_drop_dispatch; emacs_event->event.eval.object = Fcons ( lisp_event, Fcons (l_type, Fcons (l_dndlist, Qnil))); now event-stream.c catchs the misc_user and does: if (XEVENT (event)->event_type == misc_user_event) { call1 (XEVENT (event)->event.eval.function, XEVENT (event)->event.eval.object); } This calls dragdrop-drop-dispatch which is defined as: (defun dragdrop-drop-dispatch (object) (let ((event (car object)) (data (cdr object))) (message "drop at %d,%d; type %d; data '%s'" (event-x event) (event-y event) (car data) (cadr data)))) And voila: I see the info of the drag in the minibuffer. Is the loop reference evil? It seems to work fine... Regards, Oliver.

1 participants
0 comments

Re: DND for XEmacs 21 27 years

Hrvoje Niksic

Oliver Graf <ograf(a)fga.de> writes: > What I have done in the last hours is the following: > - I removed the extra drag and drop events > - I made the OffiX drop catcher in event-Xt.c generate misc-user-events > with a function of dragdrop-drop-dispatcher and the dnd-data as object. > This runs fine (now with egcs -O3 -mpentium -- without -fno-caller-saves). > > But to make the thing really work, the function called > (dragdrop-drop-dispatch) must have access to the position, button, > and modifiers where the drop happened. The question is where to put > them to get the easiest transition to the new model Why don't you add them to the event DND data? > Extending the misc_user_data by the data provided in a button_data is not > enough. If I do it this way, I must change the way XEmacs calls > misc_user_events from > /* this is from event-stream.c */ > if (XEVENT (event)->event_type == misc_user_event) > { > call1 (XEVENT (event)->event.eval.function, > XEVENT (event)->event.eval.object); > } > to > if (XEVENT (event)->event_type == misc_user_event) > { > call2 (XEVENT (event)->event.misc.function, > XEVENT (event)->event.misc.object, > event); > } > But I thing this is evil I agree that this is evil. > Another possible is to add the button, mod and pos info into the > object list. dragdrop-drop-dispatch could then create a dummy > button-xy event with the actual values (channel must also be stored > in object) so the function can use the internal functions > event-point (and others) to get the position in the buffer and the > action the user wanted. I don't understand this. > To pinpoint the whole thing again: A drop needs to know where it > happened to create the correct reaction (insert the text, change a > value in customize, create a new buffer, etc...), OK, this is clear -- but why should it create dummy events afterwards? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Don't hit a man when he's down -- kick him; it's easier.

1 participants
0 comments

Re: DND for XEmacs 21 27 years

Oliver Graf

Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > > This can be displayed (inserted, etc.) by this function. I'm now > > > > adding the needed button information to the misc_user_event. I > > > > hope this will not break anything. > > > > > > > There are actually two ways to do this: > > > > a) hardcode them into the misc_user and make the event-x, > > > > event-button, etc. function recognize this (the easy way). > > Could you please elaborate on this? I'm afraid I didn't catch all the > context. What I have done in the last hours is the following: - I removed the extra drag and drop events - I made the OffiX drop catcher in event-Xt.c generate misc-user-events with a function of dragdrop-drop-dispatcher and the dnd-data as object. This runs fine (now with egcs -O3 -mpentium -- without -fno-caller-saves). But to make the thing really work, the function called (dragdrop-drop-dispatch) must have access to the position, button, and modifiers where the drop happened. The question is where to put them to get the easiest transition to the new model (and without breaking existing stuff using misc_user_event). Extending the misc_user_data by the data provided in a button_data is not enough. If I do it this way, I must change the way XEmacs calls misc_user_events from /* this is from event-stream.c */ if (XEVENT (event)->event_type == misc_user_event) { call1 (XEVENT (event)->event.eval.function, XEVENT (event)->event.eval.object); } to if (XEVENT (event)->event_type == misc_user_event) { call2 (XEVENT (event)->event.misc.function, XEVENT (event)->event.misc.object, event); } But I thing this is evil and would certainly break something (perhaps I can create a workaround by setting for example the button value of a non-dragdrop misc_user_event to -1. So I can base the decision how to call the thing on this). Another possible is to add the button, mod and pos info into the object list. dragdrop-drop-dispatch could then create a dummy button-xy event with the actual values (channel must also be stored in object) so the function can use the internal functions event-point (and others) to get the position in the buffer and the action the user wanted. To pinpoint the whole thing again: A drop needs to know where it happened to create the correct reaction (insert the text, change a value in customize, create a new buffer, etc...), perhaps by using properties of an underlying extent (if the drop happened within it). But perhaps there is some other way? Regards, Oliver.

1 participants
0 comments

[SUCCESS] 21.0 "Repartida" XEmacs Lucid (beta38) on i386-pc-solaris2.5.1 27 years

Jason R. Mastaler

> XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/SourceTrees/xemacs-21.0-b38/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: DND for XEmacs 21 27 years

Hrvoje Niksic

Oliver Graf <ograf(a)fga.de> writes: > [Just for the others waiting] > > > > I have eleminated the special events. The x_event_to_emacs_event now > > > generates a misc-user-event with dragdrop_drop_dispatch as function > > > and a (TYPE . DATA) cons as object. And the great crowd rejoices! :-) > > > This can be displayed (inserted, etc.) by this function. I'm now > > > adding the needed button information to the misc_user_event. I > > > hope this will not break anything. > > > > > There are actually two ways to do this: > > > a) hardcode them into the misc_user and make the event-x, > > > event-button, etc. function recognize this (the easy way). Could you please elaborate on this? I'm afraid I didn't catch all the context. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- A radioactive cat has eighteen half-lives.

1 participants
0 comments

[SUCCESS] - "Repartida", SunOS 4.1.4, gcc 2.8.1 27 years

Amir J. Katz

Applied patches, etc. Clean build. No problems so far. -- /* Amir J. Katz mailto:amir＠nuke-spam.com */ /* [For e-mail, replace 'nuke-spam' with 'ndsoft'] */ /* EagleEye Control Software, LTD. http://www.ndsoft.com */ /* 'Is "tired old cliche" one?' (Steven Wright) */

1 participants
0 comments

Re: DND for XEmacs 21 27 years

Oliver Graf

SL Baur <steve(a)xemacs.org> writes: > >> How much time do you need? Personally, DND is more important to me > >> than MS Windows support, and I'm already prepared to slide the schedule > >> further to allow more MS Windows changes in. > > > Currently coding. Perhaps I can get a working new version for drops > > only until this evening. > > Cool! [Just for the others waiting] > > I have eleminated the special events. The x_event_to_emacs_event now > > generates a misc-user-event with dragdrop_drop_dispatch as function > > and a (TYPE . DATA) cons as object. This can be displayed (inserted, > > etc.) by this function. I'm now adding the needed button information > > to the misc_user_event. I hope this will not break anything. > > > There are actually two ways to do this: > > a) hardcode them into the misc_user and make the event-x, event-button, > > etc. function recognize this (the easy way). > > b) add it to the eval-object and create the necessary functions to convert > > this information to frame/buffer/point information. > > > Personally I prefer a), because rewriting all the internal pixel to whatever > > translation seems not the right way. > > > Any comments? > > None from me, I'm probably not the right person to ask though. I > trust your better judgement on this. Then I will give off another comment (and but this into xemacs-beta...): b) would also be possible, if I call all necessary functions (event-window, event-point, event-closest-point) while creating the misc-user-event and then putting the returned data also into the misc-user object. But for me a) is still the best (?) solution. Will it break something? I think not. Regards, Oliver.

1 participants
0 comments

[Success] 21.0 "Repartida" XEmacs Lucid (beta38) on i686-pc-linux 27 years

Hayashi Tanaka

Patched up from beta37. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home/tanaka/src/xemacs-21.0-b38/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

[Success] "Repartida" XEmacs (beta 38) 27 years

Rebecca Ore

Looks okay, haven't done anything yet. Didn't download the elc or info tarballs. Here's the install file: uname -a: Linux d-phletc1-1e 2.0.30 #8 Sat Apr 25 16:42:54 EDT 1998 i586 ./configure '--cflags=-g -Wall -O3 -fno-caller-saves -fno-strength-reduce -malign-loops=2 -malign-jumps=2 -malign-functions=2' '--error-checking=none' '--debug=no' '--with-mule=yes' '--with-site-lisp=yes' XEmacs 21.0-b38 "Repartida" configured for `i586-pc-linux'. Where should the build process find the source code? /home/rebecca/xemacs-21.0-b38 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -Wall -O3 -fno-caller-saves -fno-strength-reduce -malign-loops=2 -malign-jumps=2 -malign-functions=2 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files.

1 participants
0 comments

[Success] XEmacs 21.0b38 Repartida on LinuxPPC 27 years

Nobu Toge

Patched up from b37/b36. LinuxPPC kernel 2.1.24 running on PowerMac 8600. Compiled with egcs-2.90.25 980302 (egcs-1.0.2 prerelease). No glitches. Pretty smooth. ./configure '--cflags=-g -O2 -fsigned-char' '--dynamic=yes' '--error-checking=none' '--de bug=no' '--with-dialogs=athena' '--with-site-lisp' '--prefix=/usr' '--with-xfs' '--with-ca nna' '--with-mule' '--package-path=/usr/lib/xemacspack' '--with-x' XEmacs 21.0-b38 "Repartida" configured for `powerpc-unknown-linux'. Where should the build process find the source code? /home/toge/XEmacs21.0/xemacs-21. 0-b36 What installation prefix should install use? /usr What operating system and machine description files should XEmacs use? `s/linux.h' and `m/powerpc.h' What compiler should XEmacs be built with? gcc -g -O2 -fsigned-char Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. -- Nobu Toge (toge(a)accad1.kek.jp)

1 participants
0 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta May 1998