From: Hans Ronne <hronne@telia.com>
To: Eric McDonald <emcdonal@cps.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: [RFC] Possible BadWindow/BadDrawable Fix
Date: Fri, 27 Jun 2003 19:45:00 -0000 [thread overview]
Message-ID: <l03130302bb22467b512b@[212.181.162.155]> (raw)
In-Reply-To: <Pine.GSO.4.53.0306262324380.3650@cps201.cps.cmich.edu>
> So far the only way I have been able to get rid of the BadWindow errors in
>the Tcl/Tk interface on X is to destroy a window after it is withdrawn.
>
>This can be done in tkconq.tcl with:
>Or it can be done in tkmain.c with:
The second solution seems to be the best way if it works.
>And perhaps this could be wrapped in an appropriate #ifdef.
>
> This has implications for window reuse. In the case of the .newgame window,
>it doesn't really matter, but means that other windows will need to be
>recreated from scratch each time they show up in the game.
>
> My personal opinion is that new users are more likely to be scared off
>by the
>X messages than by a slightly longer delay due to window recreation. This
>delay
>is probably negligible on most modern machines, _not that I am advocating the
>neglect of older machines....
I don't think it matters under linux, either. But in MacTCL and WinTCL,
performance would suffer. However, if you use #ifdef UNIX things should be
OK.
Hans
next prev parent reply other threads:[~2003-06-27 19:19 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
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 [this message]
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='l03130302bb22467b512b@[212.181.162.155]' \
--to=hronne@telia.com \
--cc=emcdonal@cps.cmich.edu \
--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).