public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@telia.com>
To: tlow@low-shang.homelinux.com (Tom Lowshang)
Cc: xconq7@sources.redhat.com
Subject: Re: (linux) xconq errors at exit
Date: Fri, 27 Jun 2003 01:02:00 -0000	[thread overview]
Message-ID: <l03130300bb212a0d6bef@[212.181.162.155]> (raw)
In-Reply-To: <20030626225522.GA24113@low-shang.homelinux.com>

>On Thu, Jun 26, 2003 at 05:49:23PM -0400, Eric McDonald wrote:
>>
>> On a somewhat unrelated note, could you tell me if you get
>> BadWindow and BadDrawable messages on your console from games
>> that are started from the setup dialogs (as opposed to
>> starting them with -g from the command line)? Of some interest
>> is whether these are occuring with Tk 8.4 and higher....
>>
>
>If I start xconq on console, I get "X error on display :0.0:
>BadWindow (invalid Window parameter)" when xconq exits only. The
>message repeat several time.  This happens whether I use -g or
>setup dialogs.

The BadWindow/BadDrawable message is triggered by using the "wm withdraw"
command within the tcl script, and this always happens at the end of the
setup dialog (when the dialog is withdrawn). If you look at the error
messages you will find that there is one pair less if you use -g since one
tcl window less (the setup dialog) is withdrawn in that case. This is what
Eric meant. The other error messages come from other dialogs that you close
during the game or during exit.

>I also just discovered that that xconq does not handle the
>window closing well, either.  If I close a setup dialog, xconq
>does not exit until I interrupt it with control-c.  If I close
>the map window, I see the above message, followed by:
>
>Fatal error encountered. Signal 11

This is a known problem. I don't think it's related to the BadDrawable
messages.

Hans


  reply	other threads:[~2003-06-26 23:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26  0:58 emblem drawing glitches on linux Tom Lowshang
2003-06-26  0:59 ` Eric McDonald
2003-06-26  4:41   ` Tom Lowshang
2003-06-26  5:49     ` Eric McDonald
2003-06-26 16:00       ` Tom Lowshang
2003-06-26 22:55         ` Eric McDonald
2003-06-26 23:04           ` (linux) xconq errors at exit Tom Lowshang
2003-06-27  1:02             ` Hans Ronne [this message]
2003-06-27  1:33             ` Eric McDonald
2003-06-27  3:51               ` Tom Lowshang
2003-06-27 14:47                 ` [RFC] Possible BadWindow/BadDrawable Fix Eric McDonald
2003-06-27 19:45                   ` Hans Ronne
2003-06-28 17:51                     ` [Patch] " Eric McDonald
2003-06-26 16:00     ` emblem drawing glitches on linux Hans Ronne
2003-06-26 16:15       ` Tom Lowshang
2003-06-26 21:49         ` Hans Ronne
2003-07-05  0:36           ` Tom Lowshang
2003-07-05  4:39             ` Hans Ronne
2003-07-05  8:28               ` Tom Low-Shang
2003-07-05 16:11                 ` Hans Ronne
2003-07-05 16:20                   ` Tom Low-Shang
2003-07-07 18:17                     ` Hans Ronne
2003-06-26  4:35 ` Hans Ronne
2003-06-26  5:46   ` Tom Lowshang

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='l03130300bb212a0d6bef@[212.181.162.155]' \
    --to=hronne@telia.com \
    --cc=tlow@low-shang.homelinux.com \
    --cc=xconq7@sources.redhat.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).