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

Thomas Orgis wrote:

> Well, space key seems to work. Sorry for wrongly assuming that menu
> navigation works like ... everywhere else.

I'm just trying to figure out which issues are new in the last lesstif
release. Also, I forgot to mention the differences between lesstif and
openmotif, which let me use openmotif on linux. Your question however
was if one should contribute to openmotif, which I wouldn't do. Or, to
use the wording from http://www.opengroup.org/openmotif/faq.html,
"Yes, we hope to be able to make a contribution in the future, when
Motif will be made Open Source."
 
> What does not work is certain shortcut keys (the underlined characters
> in menu entries).
> Some work (copy/paste). Some not (right/left shift).

This would be new, I think.

> Also, even with the commercial Openmotif ...

I don't know whether or not Openmotif is commercial - it is maintained
by a company currently, so it may well be.  On the other hand, I think
Linux is commercial, too.  Please don't make the mistake to translate
free software into non-commercial and commercial (which is all fine)
into proprietary software.  

> >  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.

IMO there are only two possibilities: Either do it right or revert it.
Wishful thinking doesn't help. 
 
> 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? 

This is an old issue, but I vaguely recall this was fixed from inside
nedit.  Also, this old issue happened if one simply did a Ctrl+F.
There was nothing more involved.  The dialog just didn't have input
focus.  One had to click into the text field with the mouse.

> 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...

This sounds different.  Actually, I'm using lesstif mainly on MS
Windows and can't recall something like this.  Perhaps it is indeed a
setting of the window manager (like "sloppy focus" or "click to
focus").

Cheers,
Jörg

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