> I think "seems" is the key word here. The interface is not faster, > but it has a much lower latency.
"Seems" is all that matters. > > I run FC4, and using the CVS version, a straight ./configure and > > make caused a lot of lesstif errors during the [failed] compile. > > After I did ./autogen.sh; ./configure; make it worked fine. > > Odd. The usual rules are "run autogen" (which runs configure; you > don't have to run it twice) but that's all I run anyway, it would be > interesting to see what differences in configure were caused by your > autogen. I've developed on FC3 (desktop) and FC4 (laptop), although > the cvs version is from FC3. Not a big deal anyway, but I'll send you the changed files directly. > > Any time you open a menu from the menubar, the main window loses focus. It does get the focus back as soon as the menu closes, but it looks weird. > Sounds like a bug in your lesstif and/or window manager. It works > fine for me, and I've used motif and lesstif a LOT in my career and > never seen this. FWIW I use fvwm2 as my window manager. $ rpm -qa | grep -i lesstif lesstif-devel-0.93.36-5.2 lesstif-0.93.36-5.2 $ rpm -qa | grep -i motif openmotif-2.2.3-10.FC4.1 openmotif-devel-2.2.3-10.FC4.1 I'm running metacity for my wm. Matt
