search for: trackobjects

I have some conditional code based on the SWIG version. Current versions of SWIG 1.3.30 still don''t fix %trackobjects correctly so I''m going to remove the test for now so it builds correctly with my version of SWIG. Hopefully before 1.3.30 is released we''ll have a better trackobjects in SWIG. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyfo...

Hi Everyone, Good Day! I wanna to add to my blog a counter for displaying, how many times was my website visited. I would like to solve it through ruby (not GA or something like that). Is available any gem that do this task (also with checking IP address,the time of latest visited and visited count). Please Advice. Thank You. -- You received this message because you are subscribed to the

...e deleted too by the standard %freefunc. + + +// This is implemented in swig/wx.i +%{ +extern void GcNullFreeFunc(void *); +%} + +// Macro definitions. + +// Objects that are tracked but managed by WxWidgets - this is currently +// all Windows, including Frames and Dialogs +%define GC_NEVER(kls) +%trackobjects; +%feature("freefunc") kls "GcNullFreeFunc"; +%enddef + +// Strategy for windows that aren''t top-level windows. +// Here, the C++ objects are destroyed automatically by WxWidgets when the +// frame that contains them is closed and destroyed +%define GC_MANAGE_AS_WINDOW(...

Hi Have been wrestling with the frequent GC segfaults on Windows. Seems they occur b/c Windows sends Events (UpdateUIEvents, I think) with the same pointer repeatedly. These get wrapped in a ruby Event object as they are processed, and a mapping stored through SWIG''s trackobjects. However, the ruby object isn''t referenced anywhere, so gets swept and destroyed by GC when it runs. For some reason, the mapping isn''t removed, so the next time the same Event object is sent for processing (ProcessEvent), SWIG tries to retrieve a destroyed object, and segfaul...

...atures for marking and tracking. So my first question is: 1) What''s the status of the handcoded memory management (especially in wx.i and fixdeleting.rb)? Will current SWIG do everything we need in terms of linking ruby to c++ objs, and preventing c++ objects being destroyed twice, if %trackobjects is enabled? Is this the route we should go? What''s especially useful on the wiki page is the clear explanation of the kind of situations that might create problems. It''d be useful to understand better which of these might be causing the segfaults we''re seeing. So: 2...

SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until 1.3.30, unless I can hack together a nasty workaround for a problem with the object tracking. It seem that each SWIG module gets its own hash for tracking objects. This means that, for example, you create a find dialog (in FindReplaceDialog.cpp) events you get from it (from FindDialogEvent.cpp)

Hi, in my path of getting the controls sample to work nicely, I fixed some classes on the way, see the attached diffs. I had some difficulties, but could track down all stupid bugs and am now almost happy with the code :) (I had the complete ImageHandler hieracy implemented at some time, but than I discovered the error was not in unloaded ImageHandlers but in the controls-program which does not

Alex, I was getting the following crashes when editing cells in a grid: ./init.rb:1072:in `main_loop'': undefined method `begin_edit'' for "_p_wxEvent":String (NoMethodError) from ./init.rb:1072 but only after the first App GC mark phase. So I changed all the GridCell*Editor.i files from GC_MANAGE to GC_MANAGE_AS_EVENT. Which stopped the crashing. My question

Hi all Just a quick update on recent SVN activity: * added Sound and CollapsiblePane classes * added the XRC tool to wxSugar * fixed some XRC bugs in Window * added syntax sugar for event handlers and list-like controls * added some missing methods in Sizer Sean - I''m away for about 10 days from this weekend, and I''m thinking of doing a 1.9.2 release in the next day or two.

...2007-07-04 19:32:50 UTC (rev 1107) +++ trunk/wxruby2/swig/memory_management.i&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp2007-07-04 22:50:43 UTC (rev 1108) </span><span class="lines">@@ -75,6 +75,16 @@ </span><span class="cx"> %trackobjects; </span><span class="cx"> %enddef </span><span class="cx"> </span><ins>+// Sizers attached to windows are automatically destroyed by wxWidgets, +// so they should not be deleted. +// +// TODO - orphaned/unattached sizers are not automatical...