May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Oliver Graf

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > | It's up to the application to initiate a drag operation. The win32 user > | interface guidlines recommend that the application should initiate a > | drag operation when the user clicks and holds the left-button (with or > | without modifiers) within selected text. Most applications also initiate > | a drag when the right button (button3 in XEmacs) is used in the same > | way. > > Let me pick a nit. Drag is initiated after mouse is moved minimum distance > with a button down. This is also one of my favorites. Needs some changes to the mouse-select-some-region stuff... > | On dropping text, the text should be copied if the Ctrl modifier is held > | down and should be moved if Ctrl isn't down. Mod and Shift are ignored. > | Some applications display a popup menu when text is dropped with the > | right button: the menu offers the user the choice of copying or moving > | the text. We probably don't need to bother with this and can just treat > | a right-button like a left-button. The button and modifier state is > | ignored for file drops. > > Not exactly. They may have the same meaning for drop targets which are > file containers. What does dropping a file on a dired buffer mean? My current plan to implent the drop API goes the following way: - a drop is received by the protocol depended code (certainly c) - the drop is converted to a misc-user-event with dragdrop-drop-dispatch as function ** until here it is implemented ** - dragdrop-drop-dispatch (I' currently working on this -- expect patch this evening): + looks if the drop is inside some buffer yes: * check for a extend at point that defines dragdrop-drop-rules and if it's there, do whatever it asks * check for a buffer local variable called dragdrop-drop-rules and if there is one, do whatever it asks * do the some for the mode * look for some global * do the default stuff no: * semilar to the yes part Note: how this rules look like is still open... Drop (and later drag) data is always one or more URLs or MIME data. This seems to be the best way to handle data application independant in a heterogenous environment. The protocol code has to do the proper conversions. > Having a menu displayed on a right-button drop is a big plus. Pie in the > sky but the DND abstraction should not deny this. Not exactly, cause it depends on the code what the code does. A popup is certainly possible. Regards, Oliver.

1 participants
0 comments

[Success] 21.0 "Repartida" XEmacs Lucid (beta38) on i386-pc-cygw in32 27 years

Ian MacKinnon

> XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/xemacs-21.0-b38/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT TECH007 4.0 19.1 i686 unknown ./configure '--site-includes=/usr/local/include/' XEmacs 21.0-b38 "Repartida" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /usr/xemacs-21.0-b38 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include/ Compiling in support for XAUTH. Compiling in support for XPM images. 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 support for GNU DBM. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /usr/xemacs-21.0-b38/beta.err does not exist! --- Ian

1 participants
0 comments

[SUCCESS] 21.0 "Repartida" XEmacs Lucid (beta38) on hppa1.1-hp-hpux10.20 27 years

Peter Windle

using gmake still; i'll give vanilla HP make a go next time > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /local/xemacs-beta/Installation: > (Output from most recent run of ./configure) uname -a: HP-UX sdlhpp63 B.10.20 A 9000/778 2006473329 two-user license ./configure '--site-includes=/opt/audio/include -I/usr/dt/include -I/usr/local/include' '--site-libraries=/opt/audio/lib -L/usr/dt/lib -L/usr/local/lib' '--x-includes=/usr/include/X11R6 -I/usr/include/Motif1.2_R6 -I/usr/contrib/X11R6/include' '--x-libraries=/usr/lib/X11R6 -L/usr/lib -L/usr/contrib/X11R6/lib' '--with-scrollbars=lucid' '--with-menubars=lucid' '--with-gnu-make' '--package-path=/local/packages' '--gung-ho' XEmacs 21.0-b38 "Repartida" configured for `hppa1.1-hp-hpux10.20'. Where should the build process find the source code? /local/xemacs-beta What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/hpux10.h' and `m/hp800.h' What compiler should XEmacs be built with? cc -O +Onolimit -Ae +Z -z 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/dt/include /usr/include/X11R6 -I/usr/include/Motif1.2_R6 -I/usr/contrib/X11R6/include /usr/contrib/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib/X11R6 -L/usr/lib -L/usr/contrib/X11R6/lib Additional header files: /opt/audio/include -I/usr/dt/include -I/usr/local/include Additional libraries: /opt/audio/lib -L/usr/dt/lib -L/usr/local/lib 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 GNU DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /local/xemacs-beta/beta.err does not exist!

1 participants
0 comments

Re: b38: Tiff support misdetected 27 years

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > I don't know beyond what I already wrote. I just built a 3.4-beta37 > libtiff and I need to do some more poking around. > > Uh, oh. > > $ nm libtiff/libtiff.so.3.4.037 | > egrep '(_TIFFmalloc|TIFFClientOpen|_TIFFfree)' > 0001b290 T TIFFClientOpen > 0001f884 T _TIFFfree > 0001f7dc T _TIFFmalloc > > All those symbols are still in libtiff/tiffio.h too. > > Are you perhaps mixing headers from an ancient TIFF with a modern > .so? You mean the reverse: modern headers with an ancient .so (the link phase fails for me)? Maybe. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Sauron is alive in Argentina!

1 participants
0 comments

[SUCCESS] Russian White-pre1 IRIX 6.2 27 years

Paul Bibilo

I cvs updated everything. uname -a: IRIX dr2 6.2 03131015 IP22 ../configure '--site-libraries=/usr/local/lib' '--site-includes=/usr/local/include' '--gung-ho' '--cflags=-O2' '--with-mule=yes' '--error-checking=none' '--debug=no' '--package-path=/devdisk/d54man/gnu/xemacs-beta/packages' XEmacs 21.0-b39 "Russian White-pre1" configured for `mips-sgi-irix6.2'. Where should the build process find the source code? /tmp_mnt/devdisk/d54man/gnu/xemacs-beta/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/irix6-0.h' and `m/iris4d.h' What compiler should XEmacs be built with? cc -O2 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? Where do we find X Windows libraries? Additional header files: /usr/local/include Additional libraries: /usr/local/lib Runtime library search path: /usr/local/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 GNU DBM. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. OK so far, -- Paul Bibilo, Delcam plc, | Tel: +44 121 766 5544 Talbot Way, Small Heath, Birmingham, | Fax: +44 121 766 5511 England, B10 0HJ. _____|_____ ICBM-mail: 52 17N 1 30W #include <disclaimer.h> | BLAT FOOP |

1 participants
0 comments

Re: b38: Tiff support misdetected 27 years

SL Baur

Martin, I'm not going to apply the patch you posted for this, I think I've found a better way to do it. The TIFFLIB_VERSION symbol is what we should be looking at. Hrvoje Niksic <hniksic(a)srce.hr> writes: > SL Baur <steve(a)xemacs.org> writes: >> > It appears that I have an older TIFF library, so linking fails: >> >> > symbol in file >> > _TIFFmalloc glyphs-eimage.o >> > TIFFClientOpen glyphs-eimage.o >> > _TIFFfree glyphs-eimage.o >> > ld: fatal: Symbol referencing errors. No output written to temacs >> >> Just how old is your libtiff? > `ls' says "Sep 23 1997", but that has little relevance to the actual > libtiff version. >> Perhaps it's time you considered upgrading? > I'll upgrade, that's out of the question -- but XEmacs shouldn't > misdetect the old library version; it should simply assume there is no > TIFF support. Looking that way, it's a good coincidence that I have > the old version, so we were able to fix that bug. O.K. Look in tiff.h and tiffio.h. What is TIFF_VERSION (tiff.h) and TIFFLIB_VERSION (tiffio.h)? I see: tiff.h: #define TIFF_VERSION 42 tiffio.h: /* * This define can be used in code that requires * compilation-related definitions specific to a * version or versions of the library. Runtime * version checking should be done based on the * string returned by TIFFGetVersion. */ #define TIFFLIB_VERSION 19960307 /* March 7, 1996 */

2 participants
1 comments

Re: b38: Tiff support misdetected 27 years

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > SL Baur <steve(a)xemacs.org> writes: >> Uh oh. Exactly what version of tiff are you running? > How do I find out? I didn't compile the library... I don't know beyond what I already wrote. I just built a 3.4-beta37 libtiff and I need to do some more poking around. Uh, oh. $ nm libtiff/libtiff.so.3.4.037 | egrep '(_TIFFmalloc|TIFFClientOpen|_TIFFfree)' 0001b290 T TIFFClientOpen 0001f884 T _TIFFfree 0001f7dc T _TIFFmalloc All those symbols are still in libtiff/tiffio.h too. Are you perhaps mixing headers from an ancient TIFF with a modern .so?

1 participants
0 comments

Re: b38: Tiff support misdetected 27 years

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Uh oh. Exactly what version of tiff are you running? How do I find out? I didn't compile the library... -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth

1 participants
0 comments

Re: b38: Tiff support misdetected 27 years

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > I see: > #define TIFFLIB_VERSION 19970127 /* January 27, 1997 */ Uh, oh. I just downloaded tiff-v3.4beta037 (a 3.4 beta is later than 3.4 proper, help?) We're compatible with what appears to be a (very old) version of libtiff. The newer version of the library does indeed not have the symbols your link was complaining about. Um, O.K. TIFFLIB_VERSION is definitely the right symbol to look at. Now what have those functions been renamed to?

1 participants
0 comments

Re: b38: Tiff support misdetected 27 years

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: >> tiffio.h: >> /* >> * This define can be used in code that requires >> * compilation-related definitions specific to a >> * version or versions of the library. Runtime >> * version checking should be done based on the >> * string returned by TIFFGetVersion. >> */ >> #define TIFFLIB_VERSION 19960307 /* March 7, 1996 */ > I see: ... > tiffio.h: > /* > * This define can be used in code that requires > * compilation-related definitions specific to a > * version or versions of the library. Runtime > * version checking should be done based on the > * string returned by TIFFGetVersion. > */ > #define TIFFLIB_VERSION 19970127 /* January 27, 1997 */ Uh oh. Exactly what version of tiff are you running? I thought I was running a canonical, latest and greatest tiff 3.4? > which is quite strange, because it is supposed to mean that I have a > *later* tifflib than you do. Weird! It's a good thing you reported this. There appears to be more here than I originally thought.

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