Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

wxSmith development

<< < (5/34) > >>

mandrav:
You may want to look at wxWindow::RemoveEventHandler() and use it in the widget's dtor...

Yiannis.

tiwag:

--- Quote from: byo ---You must compile both C::B and wxSmith with same version of wxWidgets. Currently I'm using wx 2.4 and I don't know if it will work properly uunder wx 2.6
--- End quote ---


Thanks for the info,
OK i'll try it with the newest cvs version to compile with wx242,
the one version i got from cvs a few days ago wasn't able to compile with wx242,
a few methods only available in wx260 had been used, if i remember correctly.

--tiwag

[edit]
to make a long story short:
fresh download from cvs,
built wxsmith with wx242,
updated codeblocks build,
it runs without issues,
now i have to find out how it works ... ;-)

mandrav:
byo, just a note until I write a proper "developer's guide"  :oops:

When you 're using event handlers for C::B generated events (like EVT_PROJECT_OPEN, etc) always call event.Skip() on the event object. It seems that you don't do this now and when I load the wxSmith plugin, most event handlers in the event handling chain don't see those events.

Yiannis.

byo:

--- Quote from: mandrav ---
When you 're using event handlers for C::B generated events (like EVT_PROJECT_OPEN, etc) always call event.Skip() on the event object.
--- End quote ---


 :oops: Didn't noticed that. Will fix soon (just need to fix incompatibilities with new eeditor system :) )

mandrav:
No problem. It's my fault anyway:

--- Quote ---just a note until I write a proper "developer's guide"
--- End quote ---



--- Quote ---just need to fix incompatibilities with new eeditor system
--- End quote ---

Did you see it? Any comments?

Yiannis.

Navigation

[0] Message Index

[#] Next page

[*] Previous page