> Thanks for doing this. I ran it and it seems MUCH faster than the > Xaw or Gtk versions. A couple of notes/questions:
I think "seems" is the key word here. The interface is not faster, but it has a much lower latency. What I do is register an idle proc with the Xt layer when "stuff happens". Then, when the system is otherwise idle, it checks to see what needs to be updated. That way, there is as little as possible happening between user events, and the redraw loop never "falls behind". It takes longer to update the screen, but you don't do it as often, and feedback seems quicker. It also lets us optimize the common cases of exposures and crosshairs, since we have guaranteed backing store in the pixmap we use. I think the idle procs, when used properly, are one of my favorite parts of Xt. One of my pipe dreams is to use the SHM extension to move the pixmaps around, which may allow for alpha blending of layers (i.e. translucent ground planes). The idle proc trick allows me to spend more time in redraw, if it makes it more usable it would be worth it. > 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. > Doing "print layout" with an empty design caused a segfault. Sigh. Probably looking for the layout name. Yup: 0x080a0de7 in ps_get_export_options (n=0x80da33c) at hid/ps/ps.c:73 73 buf = (char *)malloc(strlen(PCB->Filename) + 4); The other HIDs have special tests for this. > Is there a difference between "print layout" and "export to ps"? Not on unix, since unix uses postscript for printing. When complete, "print" will queue it also. Under Win32, however, printing is *vastly* different than exporting to postscript, since printing uses the GUI code to render pages. > Any time you open a menu from the menubar, the main window loses focus. 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. > Has this version kept up with the changes to the core in the regular > CVS version that have happened during its development? Yes. There haven't been that many. > Why didn't you just branch in the same CVS? Lots of file moving, deleting, and renaming, things CVS is bad at. Most of the major work happened outside even my local cvs; I put it in my local repository only because it's easier for people to keep up with my changes that way. When it settles down enough (read "when the gtk interface is added back in") I'll commit everything to the sourceforge repository and delete mine. Plus, it's a LOT faster for me to use a "local to me" repository.
