On Tue, 5 Nov, 1996, Michael Schumacher wrote:
> a Xterm...is reparented by a Tk frame widget and packed into another
> toplevel. Unfortunately, the Xterm decorations won't disappear and fill
> the whole background of the current screen.
Hi, Mike --
Well, that certainly is unattractive, isn't it? But it *is* big.
Seriously, I haven't seen any replies on the mailing list; have you
gotten any private e-mail responses about this problem?
I spent a couple of late evenings trying to track the problem down,
without much luck so far. I'm not familiar with what tksteal is doing
internally - which extension does this belong to, and what version of Tk
is your special wish based on? You'd think some other Tk apps would be
stumbling across this, wouldn't you?
I couldn't find any workarounds. Of course, since the orphaned frame
still responds to window controls, you can get rid of it by closing it, but
that's hardly what you want to tell users they have to do.
With a little hack tracing (looking specifically for a window carrying
the title "Tgdb debugee"), I'm able to catch the UnmapNotify event that fvwm
should be honoring (and isn't) , but I can't yet tell what distinguishes this
particular window/event from a variety of others that fvwm wants to ignore, and
I never see a ReparentNotify coming through. There are significant v1->v2
changes in this area; I'm not familiar with their history, so puzzling
this out is slow going. Can any fvwm old-timers out there shed any light on
this area?
If you've gotten any further info on this, or a fix, please let me
know. Otherwise, I'll continue looking into it as time permits.
Cheers,
Bob Woodside
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Nov 08 1996 - 20:23:16 GMT