public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: xfig and mwm problems ...
Date: Tue, 13 Jan 2004 22:32:00 -0000 [thread overview]
Message-ID: <40047214.4010100@msu.edu> (raw)
In-Reply-To: <4004221A.1020706@purdue.edu>
The man has a point: I just tried to duplicate the problem and succeeded
in duplicating the problem :)
Okay, the reason this problem exists is due to the stupid VendorShell
that is used by Xt. LessTif overrides VendorShell with its own and we
had to write a hack to make this work on Cygwin/X.
Unfortunately, Xaw3d also overrides the VendorShell with its own
version. However, it appears that I got a little too busy right around
the time that I was going to release a patched Xaw3d library... I have
the updated version built in my local tree, but I never finished testing
it or releasing it. :) I just tested the fix and it solves your problem.
Thanks for putting up with a forgetful developer... I had this email all
typed up, explaing how there might be a problem since Xaw3d and LessTif
both override the VendorShell. Then I thought that I had better confirm
that Xaw3d had actually been released with that fix; it hadn't, so I had
to rewrite the whole email. :)
Xaw3d-1.5D-5 is coming soon to a mirror near you and will fix your
problem with xfig and mwm.
Harold
B. Marchand wrote:
> I appear to have the same version of lesstif as you have listed below. I
> take it you cannot duplicate this problem?
>
> --B.
>
>> Well, there is one more thing you should check:
>>
>> $ cygcheck -c lesstif
>> Cygwin Package Information
>> Package Version Status
>> lesstif 0.93.91-5 OK
>>
>>
>> Make sure that you have that same version of lesstif (it includes mwm).
>>
>> Harold
>>
>> B. Marchand wrote:
>>
>> Well, after having obtained the most recent packages:
>>
>> Cygwin Package Information
>> Package Version Status
>> Xaw3d 1.5D-4 OK
>> xfig 3.2.4-5 OK
>> XFree86-bin 4.3.0-8 OK
>>
>>
>>
>> I find I still have the same problem. However, as I said before,
>> it only happens if I'm running the motif window manager (mwm). It
>> is otherwise not an issue under twm or if I run startxwin.bat.
>> Thanks for all your help.
>>
>> --B.
>>
>
>
next prev parent reply other threads:[~2004-01-13 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 21:53 B. Marchand
2004-01-13 22:32 ` Harold L Hunt II [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 23:40 B. Marchand
2004-01-13 18:12 B. Marchand
2004-01-13 20:54 ` B. Marchand
2004-01-13 21:01 ` Harold L Hunt II
2004-01-13 17:55 B. Marchand
2004-01-13 17:59 ` Harold L Hunt II
2004-01-13 16:55 B. Marchand
2004-01-13 17:22 ` Harold L Hunt II
2004-01-13 16:51 B. Marchand
2004-01-13 16:53 ` Harold L Hunt II
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40047214.4010100@msu.edu \
--to=huntharo@msu.edu \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).