[Xastir] Good news, Bad news...

Ryan Tourge k2rrt.lists at gmail.com
Mon Nov 12 20:41:17 EST 2007


Tom can you explain how to do that? I'll give it a try.

I'm running Ubuntu 7.10 Gutsy Gibbon. The binary is giving the lesstif
errors. and I'm having some other issues compiling from source (7.04
worked so much better).

On Nov 12, 2007 5:53 PM, Tom Russo <russo at bogodyn.org> wrote:
> On Mon, Nov 12, 2007 at 03:49:04PM -0700, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> > On Mon, Nov 12, 2007 at 02:54:24PM -0700, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> > > On Thu, Nov 08, 2007 at 11:25:02PM -0500, we recorded a bogon-computron collision of the <rtg at aapsc.com> 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?
>
>
> --
> 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
> Xastir at xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>



-- 
Ryan Tourge - K2RRT



More information about the Xastir mailing list