2:04 p.m.
Keyboard events from external client window do not reach xemacs
(XtAppProcessEvent inside xemacs does not return). Mouse events are
OK (XtAppProcessEvent returns and all keyboard input handled
properly). When I use Xt external client, keyboard events are always
lost. When I use Xm external client, initially this also happens, but
after some mouse actions in client window it inpredictably becomes OK.
Client program is always the same, it is just linked with different
libextcli.
X environment: x11 5, motif 1.2 (SCO xds 5.2.5h, SCO BaseX 5.1.1b)
`Installation':
uname -a: SCO_SV d-fens 3.2 2 i386
../xemacs-21.1/configure '--compiler=gcc-2.95.2' '--prefix=/usr'
'--debug' '--error-checking=all' '--external-widget'
'--with-socks' '--verbose'
XEmacs 21.1.12 "Channel Islands" configured for
`i586-unknown-sco3.2v5.0.2'.
Where should the build process find the source code? /home/gin/xemacs-21.1
What installation prefix should install use? /usr
What operating system and machine description files should XEmacs use?
`s/sco5.h' and `m/intel386.h'
What compiler should XEmacs be built with? gcc-2.95.2 -g -O99 -mpentium
-Wall -Wno-switch
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? /usr/lib
Compiling in support for SOCKS.
Compiling in support for XPM images.
Compiling in support for PNG image handling.
Compiling in support for (builtin) GIF image handling.
Compiling in support for JPEG image handling.
Compiling in support for TIFF image handling.
Compiling in support for X-Face message headers.
Compiling in support for DBM.
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.
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: ---------------------------------------------------------
4:18 p.m.
New subject: external widget in 21.2.38
External widget behavior is a bit better. Xm external client works
entirely OK: just after calling (make-frame) external widget window
begins responding to all mouse and keyboard events. Xt external
client behaves the same way: mouse events from it reach xemacs, but
keyboard events do not.
Removing regular X frame by just closing its top-level window using
window manager works normally. However, with external frame this is
not the same. After doing so xemacs hangs like this:
#0 0x821441f in _r_select ()
#1 0x80316a2b in _XWaitForReadable () from /usr/lib/libX11.so
#2 0x80316f0e in _XRead () from /usr/lib/libX11.so
#3 0x80317520 in _XReply () from /usr/lib/libX11.so
#4 0x8031456a in XSync () from /usr/lib/libX11.so
#5 0x81c7153 in expect_x_error ()
at xemacs-21.2/src/device-x.c:1069
#6 0x81d465b in x_delete_frame (f=0x8596c00)
at xemacs-21.2/src/frame-x.c:2676
#7 0x81245dd in delete_frame_internal (f=0x8596c00, force=137163776,
called_from_delete_device=0, from_io_error=9256)
at xemacs-21.2/src/frame.c:1533
#8 0x812c6c6 in io_error_delete_frame ()
at xemacs-21.2/src/frame.c:1654
#9 0x80f440e in execute_internal_event (event=142460044)
at xemacs-21.2/src/event-stream.c:2931
#10 0x80f6815 in Fdispatch_event (event=142460044)
at xemacs-21.2/src/event-stream.c:4169
#11 0x809a4e8 in Fcommand_loop_1 ()
at xemacs-21.2/src/cmdloop.c:583
#12 0x809a786 in command_loop_1 ()
at xemacs-21.2/src/cmdloop.c:494
#13 0x80c2c1b in condition_case_1 ()
at xemacs-21.2/src/eval.c:1651
#14 0x809a8ef in command_loop_2 ()
at xemacs-21.2/src/cmdloop.c:256
#15 0x80c2ae0 in internal_catch ()
at xemacs-21.2/src/eval.c:1317
#16 0x8099d4e in initial_command_loop (load_me=9256)
at xemacs-21.2/src/cmdloop.c:305
#17 0x80b4520 in sort_args (argc=1, argv=0x8047894)
at xemacs-21.2/src/emacs.c:2253
#18 0x80b64dc in voodoo_free_hook ()
at xemacs-21.2/src/emacs.c:2682
#19 0x807be4b in _start ()
One can force _XReply () and XSync () to return by debugger and
continue. Doing so causes XmuPrintDefaultErrorMessage to emit several
`unexpected async reply' messages. Then xemacs hangs a bit later in a
similar way:
#0 0x821441f in _r_select ()
#1 0x80316a2b in _XWaitForReadable () from /usr/lib/libX11.so
#2 0x80316f0e in _XRead () from /usr/lib/libX11.so
#3 0x80317520 in _XReply () from /usr/lib/libX11.so
#4 0x8031456a in XSync () from /usr/lib/libX11.so
#5 0x81c7180 in x_error_occurred_p ()
at xemacs-21.2/src/device-x.c:1078
After forcing XSync () to return again it continues without visible
flaws.
X environment: x11 5, motif 1.2 (SCO xds 5.2.5h, SCO BaseX 5.1.1b)
6:34 p.m.
New subject: external widget
What set of X events is expected to reach MaskableEventHandler in
client and get re- sent to xemacs? This is not the case for KeyPress
events. In Motif external client they do not reach external client
app if mouse pointer is in window of EmacsFrame widget. Otherwise
they get into window of EmacsShell widget (shared with external client
widget) and get re- sent. In Xt external client they never reach
external client app and xemacs never receives them.
2:14 a.m.
New subject: external widget
>>>> "Golubev" == Golubev I N
<gin(a)mo.msk.ru> writes:
Golubev> What set of X events is expected to reach
Golubev> MaskableEventHandler in client and get re- sent to
Golubev> xemacs?
I don't think anybody knows. As far as the release plans are
concerned, that code is undocumented bitrot. Ben Wing wrote it; I'll
ask him when I talk to him next. You can email him <ben(a)666.com> but
he's way backlogged. Jamie Zawinski's page (IIRC
http://www.jwz.org/doc/xemacs-wish-list.html, or maybe s/doc/docs/)
has some suggestions for improving the external widget code. I plan
to add this to the "for future development" docs in the release pages
but it's low priority.
If you find out anything, let us know.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
1:43 p.m.
New subject: external widget
Jamie Zawinski's page (IIRC
http://www.jwz.org/doc/xemacs-wish-list.html, or maybe s/doc/docs/)
has some suggestions for improving the external widget code.
The correct URL is <http://www.jwz.org/doc/xemacs-wishlist.html>;. It
assumes that at time of writing (in v. 19.14 or 20.2) it worked
reliably, which was not the case. The `bitrot' has just occured at
least in '96.
2 p.m.
New subject: external widget
At 13:42 18/01/01 +0000, Golubev I. N. wrote:
> Jamie Zawinski's page (IIRC
> http://www.jwz.org/doc/xemacs-wish-list.html, or maybe s/doc/docs/)
> has some suggestions for improving the external widget code.
The correct URL is <http://www.jwz.org/doc/xemacs-wishlist.html>;. It
assumes that at time of writing (in v. 19.14 or 20.2) it worked
reliably, which was not the case. The `bitrot' has just occured at
least in '96.
Hey, I never saw this and (8) is remarkably similar to the gutters.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
9056
days inactive
9174
days old
5 comments
3 participants
participants (3)
-
Andy Piper -
Ilya N. Golubev -
Stephen J. Turnbull