Re: menus stay where first activated (on XQuartz)

2016-06-07 Thread Rhialto
On Tue 07 Jun 2016 at 18:19:05 +0200, Rhialto wrote:
> By the way, the first time I tried it, XQuartz miserably fails with
> xeyes. (Somehow it seems to work better now). So I don't expect it to be
> perfect and anything that goes wrong may easily be an XQuartz problem.

Ah, on the second try it fails again. When you move and/or resize the
xeyes window, it doesn't properly refresh its displayed bits.

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert  -- Wayland: Those who don't understand X
\X/ rhialto/at/xs4all.nl-- are condemned to reinvent it. Poorly.


signature.asc
Description: PGP signature


Re: menus stay where first activated (on XQuartz)

2016-06-07 Thread Rhialto
[wo...@planix.com removed from To: because his mailer doesn't like my
mailer]

On Sun 22 May 2016 at 19:07:41 -0700, Greg A. Woods wrote:
> when a native OSX Xquartz compiled ctwm-3.8.2 runs locally

How do you run ctwm locally on the Mac? At work I have XQuartz too but
if I try to start ctwm I get

$ ./build/ctwm --replace
./build/ctwm:  another window manager is already running on screen 0?
./build/ctwm:  unable to find any unmanaged screens

By the way, the first time I tried it, XQuartz miserably fails with
xeyes. (Somehow it seems to work better now). So I don't expect it to be
perfect and anything that goes wrong may easily be an XQuartz problem.

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert  -- Wayland: Those who don't understand X
\X/ rhialto/at/xs4all.nl-- are condemned to reinvent it. Poorly.


signature.asc
Description: PGP signature


Re: Menu painting (was Re: Spring snapshot has sprung [Works on SL6.7 .. but,,,])

2016-06-07 Thread Matthew D. Fuller

On Mon, Jun 06, 2016 at 11:24:31PM +0100 I heard the voice of
Aaron Sloman, and lo! it spake thus:
> 
> Apologies for not getting round to your previously suggested test
> using remote access.

Oh, that's all right.  It wouldn't have told us as much as I unearthed
here anyway; would probably just have said "Yup, it's the X server".


> > What _I_ wind up with is the background of each line not being set
> > (just left black) until the mouse goes over it.
> 
> That's what I found, but perhaps I misdescribed it.

I read you as saying there was _nothing_ there; I got the foreground,
just not the background.  Though I s'pose if your foreground color
were black (or whatever you get in the back), it winds up looking like
the same thing.


> I don't know enough to have an informed opinion on that but do
> recall deciding a few years ago that optimising code for refreshing
> the xterm window used in a text editor was no longer necessary
> because refreshing the whole window was so fast, even over a network
> connection.

Yeah.  A lot of things have changed since Tom typed "vi twm.c" in
1986.  Some optimizations reasonable or necessary then are neither
now, and some of them actually make things worse now.  Things like the
default BackingStore state are really due for re-evaluation.  It's on
my todo list, but there are only so many years in the day, sadly.
Shoot, if I were writing a WM from scratch nowadays (which oddly, I
did think about a time or two), I wouldn't even write it in C.

(Don't worry, my project to reimplement ctwm in perl is currently on
hold for the summer  ;p)


> Perhaps there was a time when the problem now on SL existed on
> Fedora, and settingthat variable fixed it.

Could be.  I'm presuming it's a bug in the X server stack somewhere in
that version.  I did a little poking around X.org's bug tracker to see
if I could find a trace, but didn't come up with anything (and didn't
care enough to try TOO hard).


> I have no recollection of adding that entry!

Pfft.  As if your config files aren't under version control, so you
can't just go read the commit log;p


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.