Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
wxSmith development
cyberkoa:
--- Quote from: rickg22 ---cyberkoa: Remember that in TortoiseCVS you can "update special", and pick a specific TAG (C::B version) to use. It's better if you work on the 1.0beta-final, so at least we can be sure that it's not C::B source code that's causing the problems. (OH - and delete all the plugin dlls from both the devel and output subdirectories).
--- End quote ---
I already manage to compile in the my company's PC and run CB properly after getting the hints from madrav that need to run update.bat after finish compiling .
I am now trying at my Laptop .. hopefully everything is ok.
rickg22:
Perhaps we should make a wiki article about compiling codeblocks for windows :)
tiwag:
i just compiled wxsmith using wxWidgets 2.6.0 dll's
and tried to run it with my build of C::B, which uses wxWidgets 2.4.2 dll's,
and C::B crashes during start, when i remove the wxsmith addin, C::B starts normal.
Can someone confirm this behaviour plz ?
i'm not shure, if it's necessary to build C::B using wx260 in order to run wxsmith ?
thanks,
tiwag
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
byo:
Got one question - If i've added new Event Handler through wxWindow::PushEventHandler function it is not deletet automatically when widget is. Tried to do it through EVT_CLOSE but this is not generated for widgets. Any idea how to do it automatically ? Maybe creating one global event handler for all widgets but in such case there woul be need to create mapping wxWindow -> wxsWidget ans I think it's not a good Idea. Additional handler can also be removed while deleting preview but it may cause some realy bad errors
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version