[cells-gtk-devel] Lispworks Linux / SuSE 9.2

[Kenny Tilton]

Peter Denno wrote:

>Of course, it now sits in the outer loop forever -- even after killing the 
>window. If I knew what a quit-app event looked like, maybe I could exit the 
>outer loop. 
>
I do not think a window close entails an application quit, tho that is 
how things work on windows. Gtk is more general. So what you want to do 
(to get that win32 behavior) is call gtk-main-quit when you see a window 
closing (I was too lazy to look that up, but I think there must be some 
way to intercept that).

If this were a Mac app, there would be an explicit "quit app" command 
unrelated to windows closing. The handling of that by your app should 
again be gtk_main_quit.

One thing I like to do as a quicky in Cello development is bind the quit 
processing to the event key. The quit processing also sets a global 
*gtk-main-loop-exit* or some such, and then the outer loop is (loop 
while *gtk-main-loop*...)

I will look at your tree-view question next.

kt