Re: Lesstif isn't Motif [was: Dead end?]

Am Mon, 23 Mar 2009 20:29:49 +0100
schrieb Joerg Fischer <[email protected]>: 

> My feeling is now you always used Motif.  The enter key never worked
> in lesstif (use the space key instead).

I have been using openmotif, yeah. Just recently the whole issue came
up with the deprecation of libXp in Xorg, which openmotif source
doesn't handle yet (perhaps trivial fix anyway, disabling corresponding
code). And indeed, I rarely used the nedit menus, usually in the
sluggish manner of the mouse pilot.
Well, space key seems to work. Sorry for wrongly assuming that menu
navigation works like ... everywhere else.

What does not work is certain shortcut keys (the underlined characters
in menu entries).
Some work (copy/paste). Some not (right/left shift).

> To summarize, you solved two bugs in the latest 0.95.  One in
> Traversal.c, which trying to fix something else actually breaks its
> own tests (as Scott noticed).  I don't know, why you call it a hack,
> if one reverts a broken fix, btw.

Well, there could still be the original issue people wanted to fix;-)
Generally, the lesstif business  feels hackish to me because I didn't
meet someone who actually is familiar with the code. Also, even with
the commercial Openmotif there's talk from the nedit side about newer
versions breaking things.
This just does not sound healthy.

>  The other change in MenuShell.c was
> questionable right from the start, and, as xpdf shows, it is wrongly
> done, either.

Hm, so one should also revert the part that made the menu sticky...
Not the case in my build yet.

> (Putting it in with #if 1 is, well ...)  So, with the
> clipboard fix, you'll have a stable lesstif.

Hm. Only my trust in it seems to be someplace else. Perhaps it'll be
fine.

> Anyway, what you call "focus weirdness", is this just the enter key
> not working?

No, that one is really annoying: Often (after switching to the nedit
window... I switch windows a lot), the search/replace dialog, opened
via Ctrl+F does not get keyboard input.
I have to close it with the mouse, click into the nedit window to make
sure and then open the dialog again to be able to type in it.

You have any idea about that? Without that annoyance, I perhaps could
live on for some time with nedit... until the whole unicode issue gets
me again.
The non-working shortcut keys in the menus I won't miss, but keyboard
input is rather basic.
I just now verified that the whole of nedit does not get keyboard input
(as focused window) unless I click into the nedit window with the
mouse. One could try to blame that one the window manager, but I only
changed in lesstif for openmotif, not changed the window manager.
Interesting that the Ctrl+F works for nedit, but normal keyboard input
not...


Alrighty then,

Thomas.

-- 
NEdit Discuss mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknIFPkACgkQm0xSvNRG1SRbiACfSMia75UhnUizUSSRZfecftqK
T4IAn1upaM3Lc4kC1J/ItldXjTzkcVU8
=H1DL
-----END PGP SIGNATURE-----