Hey GI (fileProGI developers, that is)

[ryan at bulldogsoftware.com]

On Sun, May 01, 2005 at 05:31:09PM -0400, Fairlight said:

> > Not unless they provide/have provided a config variable to allow you
> > to do this.  
> 
> Not to digress too much, but is this actually viable from a technical
> standpoint?  What do you do, capture the window destroy event from the big
> X button and just redraw everything you had in place as if it never
> happened?  I've gotten mixed results from that X.  In ways it acts like a
> kill, but it's not a signal.  It's really a window event, but it seems more
> destructive than that, as it will take all subwindows with it.
> Ahhhh...probably because the subwindows were really TopLevel's based on the
> object that just got whacked.
> 
> Yeah, I probably answered my own question.  Just requires dilligent
> tracking then, yes?

In any Window definition you can define which buttons are visible.

-- 
Ryan Powers
Bulldog Software, Inc.
http://www.bulldogsoftware.com
-------------------------------------------------------------------------------