[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Aug 21 17:58:37 2002 
Subject:Re: Installing poplog on Madrake 8.2 
From:Jonathan L Cunningham 
Volume-ID:1020821.02 

On Wed, 21 Aug 2002 12:09:10 +0100, Stephen Isard
<S.IsardDeleteThis@ed.ac.uk> said:

>Jonathan L Cunningham wrote:
>
>> [Question 0: how could I have found
>> out I already had Lesstif?]
>
>"rpm -q Lesstif" will tell you if there's an installed package called

Oh. Yes. Thanx.

Perhaps I should have read the man pages for rpm :-).

>> (1) Does it matter? Should I replace the Lesstif with Motif?
>
>I am definitely not an authority in this area.  As far as I'm aware,
(snip)

>Since my system was working ok before I installed Lesstif, I felt fairly
>safe in removing it when it turned out to be unhelpful for Poplog.  You

Thanx for this. I decided to replace the Lesstif with openmotif -
actually I did a forced install of openmotif, because it didn't
initially occur to me that the Lesstif package was called lesstif.

In any case, forcing the openmotif to install has eliminated all the
errors I was getting yesterday.

**ADVICE to users installing Poplog on a default Mandrake 8.2**

If you want to use the motif version of poplog, install openmotif,
Poplog seems to work ok with openmotif-2.1.30-4_MLI, which I
downloaded as per the site in Aaron's install instructions. (Almost,
there was an outdated link which no doubt he will update when he
has time, but it wasn't a problem.)

Although I'm not sure that I'll continue using the motif version:
it doesn't seem to have any significant advantage over "raw" xved,
and I'll probably be using RCLIB for graphical stuff anyway.

>> [1] I already had a very old Slackware (I think) unix on an old 486,
>> but it only has 16MB of RAM, which is not enough to run X-Windows
>> and also applications at the same time.
>
>Just for the record, I can run X and poplog simultaneously on my 486
>with 16MB RAM (and swap space, under muLinux). I didn't link X into the
>libc5 poplog, to keep the size down, so I don't know how Xved would
>behave.

Yes, I think I ran your libc5 poplog on it. But I think it is going
to be much more useful to me if I can *develop* the pop11 programs in
a richer (windowed) environment. I've got used to using a mouse!

Which brings me to my next question! :-).

I suspect I'm going to have to ask this on a Linux forum, but it may
be of interest to Poplog users in case something similar happens to
them.

After realising the middle button on my Microsoft Intellimouse was
not being recognised, I attempted to update the configuration. And
got it wrong at the first attempt.

Now that I've got it working again (and better) in X-Windows all
three buttons work (all five, in fact, since the middle button
is actually a wheel, and can be rotated as well as pressed).

But xved no longer responds to mouse clicks. The status line changes
when I move the mouse over a "REF * foo" kind of thing, and if I click
a button (any button) the status changes again, but the click has
no other effect. I guess xved is processing mouse movement events,
and some other events associated with the mouse down, but for some
reason is not recognising the mouse click as "button 1" etc. Or
it could be something completely different.

Any ideas?

One other piece of information. The Mandrake graphical "mouse
configure" tool either didn't know about Intellimouses or I selected
wrong options or something. So I eventually edited a convenient
looking config file by hand (which is what got the mouse working
properly in X-Windows). Yet it seems as if the console (i.e. before
you start X-Windows -- I like to start it manually) has a different
configuration file for using the mouse.

And maybe there is yet a third configuration file that poplog uses?

I'm fairly sure xved was responding to mouse clicks before, when
I was using the wrong (two button) mouse driver. Since the rest of
X-Windows now seems to be working properly, I'm not sure to what
extent this is a poplog issue.

I was planning to download and install RCLIB next anyway, so it
might be interesting to see how that behaves. At the least, I should
be able to easily see what mouse events are being captured/sent, I
think?

Jonathan

-- 
Jonathan Cunningham (catching up with backlog)