Re: "Fix" for Progressbar crash....(and the Gutters exit?)

mb> Do we have to subclass the Athena widgets? It's that or rewrite our event loop to be compatible with a modern widget set such as GTK, isn't it? Or abandon the goal of a modern look interface. Obviously it's possible to to subclassing right (even mechanically, cf C++); we should look for enhanced Athena widget sets that do so, and recommend them, maybe even refuse to ./configure the bad ones. The problem here is that we really need a multiple inheritance mechanism (3D-ness is orthogonal to functionality like tabs and gauges) when we subclass from Athena, whereas 3D aspects are part of the base classes for modern widget sets. This was poorly thought through for Xaw3d, but maybe some of the other enhanced sets did a better job (or got lucky)? Another solution is to mandate (through configure) static linking of the 3D widget sets that cause crashes when dynamically linked to incompatible libraries. Is that feasible? (Yes, I know it probably adds >250kB to the executable. If that's what the user wants, what's wrong with it?) -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."