User forums > General (but related to Code::Blocks)

New Plugin: wxCrafter Integration with CodeBlocks

<< < (5/5)

eranif:

--- Quote ---On the long run it would be nice to have an option to set wxCrafter explicitly. :-)
--- End quote ---
Sure, I will add it

Eran

eranif:
Done, I have added configuration settings dialog that allows you to set a different path to wxCrafter. The default value is set to /usr/bin/wxcrafter on Linux and to the value that exists in the registry for Windows.

Do:

--- Code: ---git pull --rebase
--- End code ---
for the latest change

Thanks,
Eran

MortenMacFly:

--- Quote from: eranif on June 13, 2014, 03:10:39 pm ---
--- Code: ---git pull --rebase
--- End code ---
for the latest change

--- End quote ---
Working with this plugin for some time I realised its also the root of an annoyance I was not able to track down until now:

If you have this plugin enabled, you'll get this error on C::B startup:
---------------------------
Codeblocks Error
---------------------------
Resource files must have same version number!
---------------------------

I was looking for a long time which XRC files cause the version mismatch but didn't find one. Now I did by accident: It seems that you integrate XRC files as ASCII stream in the sources of the plugin that must contain a version number. As these are not proper XRC files its well hidden from the developer (me).

Would you please either make these XRC files... well... XRC files or remove the version number? In C::B all XRC files share the same (version-free) header like:
<?xml version="1.0" encoding="utf-8" ?>
<resource xmlns="http://www.wxwidgets.org/wxxrc">
[...]


Also, I would like to state again that if this was a subversion repo (probably on sourceforge) it would be easy to integrate into C::B trough an SVN external. Having this plugin on GIT and the need to self-compile it makes it well hidden.

Alpha:

--- Quote from: MortenMacFly on February 07, 2015, 08:11:21 pm ---Also, I would like to state again that if this was a subversion repo (probably on sourceforge) it would be easy to integrate into C::B trough an SVN external. Having this plugin on GIT and the need to self-compile it makes it well hidden.

--- End quote ---
Github states you can use subversion on their repositories as well.

MortenMacFly:

--- Quote from: Alpha on February 07, 2015, 08:40:40 pm ---Github states you can use subversion on their repositories as well.

--- End quote ---
Good catch! ...and it actually works!

Navigation

[0] Message Index

[*] Previous page