On Mon, Nov 12, 2007 at 09:43:42PM -0500, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > You're talking about issues with the current version of openmotif, but the > Ubuntu distribution selects the lesstiff2 package by default. On my > system, the xpdf application also depends on lesstiff2, and does not > exhibit the 'missing labels' problem.
Yep, sorry. Curt was the one who had to downgrade OpenMotif to the previous version. I use OpenMotif on Ubuntu 7.04 and haven't upgraded to 7.10 on any of my machines yet. Just bought the kid a new laptop though and it has 7.10 on it, so when I get a chance (which could be after Christmas) I'll put Xastir with OpenMotif to see if that answers the problems. I'm disinclined to go with lesstif myself because of a few issues that I know are wrong in lesstif. I agree with you somewhat about the lesstif issue: so many applications seem to feel it's a completely acceptable alternative to OpenMotif that there must be something in the way Xastir is coded that is different than those applications -- but that could just be that those applications don't use standard Motif techniques that lesstif gets wrong (xastir uses one, at least). > Rick Green, N8BJX > > On Mon, 12 Nov 2007, Tom Russo wrote: > >> On Mon, Nov 12, 2007 at 03:49:04PM -0700, we recorded a bogon-computron >> collision of the <[EMAIL PROTECTED]> flavor, containing: >>> On Mon, Nov 12, 2007 at 02:54:24PM -0700, we recorded a bogon-computron >>> collision of the <[EMAIL PROTECTED]> flavor, containing: >>>> On Thu, Nov 08, 2007 at 11:25:02PM -0500, we recorded a bogon-computron >>>> collision of the <[EMAIL PROTECTED]> flavor, containing: >>>> [missing fonts with recent versions of openmotif] >>>>> >>>>> I know the developers have been saying this is a bug in the motif >>>>> libraries, but I don't see this artifact in any other applications >>>>> which >>>>> depend on those same libraries, so there must be some component of >>>>> coding >>>>> style involved as well... >>>> >>>> I just spent ten minutes googling the issue and found this: >>>> >>>> http://bugs.motifzone.net/show_bug.cgi?id=1381 >>>> >>>> Turns out that there *is* a bug in openmotif related to labels and such >>>> that >>>> are set to insensitive with the XtSetSensitive function. We use that >>>> all >>>> over the place. They claim to have it fixed, but the fix is ifdef'd, >>>> meaning >>>> you'd have to recompile openmotif from source with that symbol defined. >>> >> [...] >>> >>> The relevant resource looks like it would be the one that sets the >>> FontType >>> in the render table, but I don't know how much of the other parts of the >>> example resource file in that bug report would be necessary to get the >>> job >>> done in Xastir. I would think it was just the one line, but not sure. >>> >>> If someone with time could read through >>> http://www.ist.co.uk/motif/books/vol6A/ch-25.fm.html >>> and see if they can make heads or tails of it enough to try something, >>> that >>> would probably be of benefit to the community. >> >> It looks like if one were to create a resource file, say, "resource.test" >> with: >> >> *.fontType: FONT_IS_FONT >> >> in it, then make xastir use it by running: >> >> XENVIRONMENT=`pwd`/resource.test /usr/local/bin/xastir >> >> then perhaps the issue might clear up. Could someone try it? >> >> > > -- > Rick Green > > "Those who would give up essential Liberty, to purchase a little > temporary Safety, deserve neither Liberty nor Safety." > -Benjamin Franklin -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
