I did a quick look through the docs and tutorial. All we have to do is trap the "delete-event" signal. This is called BEFORE the actual destroy takes place. If you return "True" then the gtkWidget will NOT be destroyed, if you return "False' it WILL be destroyed. This seems backwards to me but that is how it works.

Now working that through our Dispatch stuff might be a trick. I'll look at it tonight and see if I can't get something working.

I would like a FEW people to but it's the same ole people....however.

It would help others get used to GTK and our code.

this is probably the best step for anyone to take. Go to the gtk site and go through the Tutorial and look at the reference manual. They aren't completed docs but they can get you started.

Then if someone has an implementation, send me the code () and I'll look at the implementations.

You could also upload the code to

ftp://ftp.miraclec.com/lazarus

and then indicate it is there for review.

We could use someone to figure out how to get the destroy signal from the widget, and if the user chooses, cancel the destroy so the form doesn't close. Right now we are only reacting to events, not interacting.

Perhaps it has something to do with the gtk functions signal_connect_after and signal_connect_before but we could really use someone to look at the info (www.gtk.org) and see if they could handle implementing it.

I would like a FEW people to would help others get used to GTK and our code. Then if someone has an implementation, send me the code () and I'll look at the implementations.

Please post here if you would look at it for us.
Thanks
Shane