|
From: Vic L. <ll...@16...> - 2010-05-12 04:33:27
|
On Tue, 2010-05-11 at 14:22 -0400, Daniel Richard G. wrote: > On Tue, 2010 May 11 14:28+0800, Vic Lee wrote: > > > > So the exit delay is there to avoid unexpected exits, and I think it > > also helps to improve performance. And it works good so far. :) > > Isn't the delay a bit out of place after a user-initiated Quit action? > It doesn't make much difference if the program was launched from a GUI, > but if you're running it from a terminal foregrounded, and you want to > get back to the terminal afterward, that's a bit awkward. The menu should call "Close" not "Quit", I need to change it. Because every window runs independently and we don't actually "quit" the app. > > (Couldn't you do something like have a variable "don't exit if the > current time is less than this," and update it whenever the program > needs to go window-less for a little while?) Yes with careful design this could be done. I am just thinking this might not be that worth of doing it, especially when comes in a Telepathy plugin, things are getting more complicated (the application might run in background doing a series of chained actions for some time, getting the tube ready). > > > --Daniel > > |