ruby-****@sourc*****
ruby-****@sourc*****
2008年 4月 20日 (日) 10:38:36 JST
-------------------------
REMOTE_ADDR = 218.138.133.44
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tips_threads
-------------------------
@@ -10,39 +10,39 @@
First, force all your your Ruby threads to start from within the main loop using the standard Gtk.init method. You can call Gtk.init as many times as necessary. For example:
- Gtk.init_add do
- DBus.start_listener
- end
+ Gtk.init_add do
+ DBus.start_listener
+ end
Next, queue your Gtk activities as blocks to be called in Gtk's main thread. The following code helps with this. (Based on Mathieu Blondel's suggestion. [[http://www.ruby-forum.com/topic/125038|See this topic on the Ruby Forum for a discussion.]])
- module Gtk
- GTK_PENDING_BLOCKS = []
- GTK_PENDING_BLOCKS_LOCK = Monitor.new
+ module Gtk
+ GTK_PENDING_BLOCKS = []
+ GTK_PENDING_BLOCKS_LOCK = Monitor.new
- def Gtk.queue &block
- if Thread.current == Thread.main
- block.call
- else
- GTK_PENDING_BLOCKS_LOCK.synchronize do
- GTK_PENDING_BLOCKS << block
- end
- end
- end
+ def Gtk.queue &block
+ if Thread.current == Thread.main
+ block.call
+ else
+ GTK_PENDING_BLOCKS_LOCK.synchronize do
+ GTK_PENDING_BLOCKS << block
+ end
+ end
+ end
- def Gtk.main_with_queue timeout
- Gtk.timeout_add timeout do
- GTK_PENDING_BLOCKS_LOCK.synchronize do
- for block in GTK_PENDING_BLOCKS
- block.call
- end
- GTK_PENDING_BLOCKS.clear
- end
- true
- end
- Gtk.main
- end
- end
+ def Gtk.main_with_queue timeout
+ Gtk.timeout_add timeout do
+ GTK_PENDING_BLOCKS_LOCK.synchronize do
+ for block in GTK_PENDING_BLOCKS
+ block.call
+ end
+ GTK_PENDING_BLOCKS.clear
+ end
+ true
+ end
+ Gtk.main
+ end
+ end
Usage is very simple:
@@ -50,11 +50,11 @@
Whenever you need to queue a call, use Gtk.queue. For example:
- def my_event_callback
- Gtk.queue do
- @image.pixbuf = Gdk::Pixbuf.new @image_path, width, height
- end
- end
+ def my_event_callback
+ Gtk.queue do
+ @image.pixbuf = Gdk::Pixbuf.new @image_path, width, height
+ end
+ end
Issues: