search for: wxdebug

For debug builds we define __WXDEBUG__ and WXDEBUG=1. In the swig code we add a check for wxDEBUG to directors. My guess is we mean for one of those defines to be the other. Which one should we change? wxDEBUG-> WXDEBUG or WXDEBUG-> wxDebug? Roy

...I just checked in support for overriding App#on_assert. Mainly because I was really tired of the "looping crash" I have mentioned before, which happens on my system whenever an assert is caught by the default handler built into wx. Separate topic: wxRuby does some cool diagnostics when wxDEBUG is defined. I''m not sure we want to ship with wxDEBUG enabled, but I sure would like to have it turned on whenever I''m developing and debugging. Any thoughts on how best to let me run with it, but not to impose that on everyone else via cvs? Maybe we could have an optional config...

...ine] </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsplines << ''#ifdef wxDEBUG'' </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsplines << ''...

...&nbsp&nbsp&nbsp&nbsplines = [line] -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsplines << ''#ifdef wxDEBUG'' -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsplines << '' printf("'' + this_module + ...

I was investigating why the find dialog causes an error when you close it. It seems that wxRuby2 is returning a new ruby object when you call Event.get_dialog. This causes some big problems when you''re expecting you''re going to get back the same ruby pointer that you put in. In a brief check over the source I don''t see anything that preserves the original ruby

...t output statements all through the minimal sample and all the code was hit except for GUI event related code. I seems as everything is working fine but the GUI just does not show anything. Anyway in the process of looking for a fix I fixed some other errors that I came across. in App.i I changed wxDEBUG to __WXDEBUG__ now all the extra debug info is spit out at the command line (at least on Mac OS X, should on others also) in Window I got rid of the Clear() method which no longer exists, I am surprised we did not get a problem with this earlier. I also changed the GetFont method to the correct fo...

I see that this problem was noted a while ago (http://rubyforge.org/ tracker/index.php?func=detail&aid=251&group_id=35&atid=218) but it seems not to have received much attention. Any chance that it will be looked at anytime soon? So far, I prefer wxRuby to Ruby/Tk because of that closer coupling with the native window manager. However, the memory leak is just murdering me.

Hi all, How soon can we do our alpha (binary gem) release? 1. I would like to get the samples working a bit better, but am ok simply documenting most of the current problems. Do the samples crash every few minutes for other people? Or is it just me? I would like to have a copyright/license comment at the top of every sample file before the alpha release. 2. I would like to receive and merge a