In reply to Steve, Waldek wrote:
Have you tried the following in pop11:
uses rc_graphic;
uses rclib;
uses rc_mousepic;
rc_start();
I get the graphic window but I can't do much with it or with xved.
(I am running poplog with motif linked in at the moment -- I don't know
if that makes any difference.)
And click on window delete button? Before fix this reliably killed
Poplog process. Now for me most of the time this is no-op,
sometimes works as expected.
I find the kill action doesn't happen but can be triggered if a pop11
command is typed in.
I use the ctwm window manager (invoked from fedora xfce login).
But I can't kill the graphic window with the mouse.
If I type
ved
the graphic window disappears.
I then get an xved window but I can't do anything with it: typing has no
effect.
If I restart and type 'teach eliza' to the pop11 colon prompt, I get an
xved window with teach eliza text, but again I can't do anything with it.
If I switch to a different ctwm desktop, then return the eliza text is no
longer visible in the window. I.e. xved isn't responding to signals as it
should.
If instead of starting from pop11, I type, to the shell:
xved
(= pop11 +xved)
That starts up the xved saved image, and everything works as expected.
I conclude that the process of creating the saved image (using mkxved)
now includes additional xwindow stuff that enables xved to respond to
keyboard input and mouse actions, which are not available in the startup
saved image, and prevents xved working. On the other hand it allows plain
old ved to be used, as well as pop11 commands outside the editor.
That was the background to my remark in the previous message.
The image sizes in in $usepop/pop/lib/psv for pop11 and ved are
for pop11:
-rw-r--r-- 1 axs axs 2189712 Aug 23 11:01 startup.psv
for xved:
-rw-r--r-- 1 axs axs 477656 Aug 24 02:49 xved.psv
So xved adds about 20% extra stuff. If it were always built in to
startup.psv, with the only difference being whether they start with the
pop11 colon prompt or with xved running some users might prefer that.
But it may also be useful to keep the option to run ved in a non-graphical
environment after starting with the pop11 command.
Perhaps the raw startup.psv image created by mkstartup could be extended
to be ready to run xved properly. But I presume that would make it
equivalent to the xved saved image, except that it starts with the pop11
prompt, which may be useful for some applications where a text-only dialog
is used to specify what should go into the xved buffer when it starts up?
Head spinning... must sleep now.
Aaron
One possibility is that this
depends on window manager, so I would like to know what happens
in different setups.
I use the fvwm window manager. Killing the rc window from its menu does not
kill the Poplog process, but after the rc window has been killed a further
call to rc_start() gives an error message
: rc_start();
;;; --- XLIB IO ERROR (client killed with KillClient?)
;;; --- X server: ':0'
;;; --- Error Code: 4 (Interrupted system call)
;;; MISHAP - xioe: XLIB IO ERROR -- see above
;;; PRINT DOING
;;; DOING : <External Calls> XpwCallMethod XpwClearWindow rc_start
;;; pop_setpop_compiler
Also, before typing:
rc_destroy_widget(rc_window);
for me killed Poplog process. For me now this reliably closes
the window, and Poplog continues to run.
Me too. And if I kill the rc window that way, I can do rc_start() again with
no error message.
Hope that helps.
Steve
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
