On Fri, Nov 13, 2009 at 5:39 PM, Bram Moolenaar <b...@moolenaar.net> wrote: > Tim Starling wrote: >> GtkFileChooser is disabled in gvim, because gvim exits gtk_main() level >> 1 every time an event is received, causing GTK to write to the disk >> excessively. >> >> [snip] >> >> That turns out to be unnecessary, since all GMainLoop does is calls >> g_main_context_iteration() repeatedly, until it's time to exit. The >> actual task of registering event sources and calling select() is done by >> GMainContext, which exists whether or not a GMainLoop has been created. >> Thus by calling g_main_context_iteration() at the relevant places, vim >> can leave main_loop() unmodified. >> >> My patch does this, and removes all calls to gtk_main_quit() except the >> ones in modal dialogs. Modal dialogs are now implemented by calling >> gtk_main() once only, and allowing the button handlers to call >> gtk_main_quit(), just like in a regular GTK application. >> [snip] > > I'm very glad to see someone is picking up a GTK problem. Hardly any > work was done on GTK for a long time. > > I would appreciate it if a few people try this out and report any > problems they notice.
Given the recent removal of GTK 1 support, attached is an updated patch. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@jamessan.com> -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
fix-gtk-main.patch
Description: Binary data
