search for: wxruby_wrapwxeventinruby

...ched) using both wxPython and wxRuby. It was not my surprise that on my machine I had wxPython with an average of 97033 events/second and wxRuby with 39435 events/second. The script does not intend to have scientific rigor but it demonstrates what I meant. The patch modifies mainly the behavior of wxRuby_WrapWxEventInRuby(). One of the great bottlenecks that I could find was the C++ code calling Wx::EvtHandler.event_class_for_type() on the ruby side every time a new event is generated. I modified it to directly access the Wx::EvtHandler::EVENT_TYPE_CLASS_MAP hash (and saving it in a global variable after the first l...