#<RDoc::Comment:0x007fddbbfe8c10>
#<RDoc::Comment:0x007fddb8c8d9d8>
#<RDoc::Comment:0x007fddb80c1d70>
#<RDoc::Comment:0x007fddc736b710>
#<RDoc::Comment:0x007fddb7c90828>
#<RDoc::Comment:0x007fddc760fd68>
#<RDoc::Comment:0x007fddb747f4b8>
#<RDoc::Comment:0x007fddb72cdc78>
#<RDoc::Comment:0x007fddb56b3858>
#<RDoc::Comment:0x007fddb50ae868>
#<RDoc::Comment:0x007fddb3897f18>
#<RDoc::Comment:0x007fddb2a20f48>
#<RDoc::Comment:0x007fddb26f90b8>
#<RDoc::Comment:0x007fddb21eb418>
#<RDoc::Comment:0x007fddb21a1908>
#<RDoc::Comment:0x007fddb2184a10>
*** KNOWN BUG ***
Main event loop thread of TkAqua (> Tk8.4.9) must be the main application thread. So, ruby1.9 users must call Tk.mainloop on the main application thread.
*** ADD (2009/05/10) ***
In some cases (I don't know the description of conditions), TkAqua 8.4.7 has a same kind of hang-up trouble. So, if 8.4.7 or later, set RUN_EVENTLOOP_ON_MAIN_THREAD to true. When you want to control this mode, please call the following (set true/false as you want) before "require 'tk'". ---------------------------------------------------------- module TkCore; RUN_EVENTLOOP_ON_MAIN_THREAD = true; end ----------------------------------------------------------
*** ADD (2010/07/05) ***
The value of TclTkLib::WINDOWING_SYSTEM is defined at compiling. If it is inconsistent with linked DLL, please call the following before "require 'tk'". ---------------------------------------------------------- require 'tcltklib' module TclTkLib remove_const :WINDOWING_SYSTEM WINDOWING_SYSTEM = 'x11' # or 'aqua' end ----------------------------------------------------------
start Tk which depends on MultiTkIp