User forums > Using Code::Blocks

Resource files

<< < (3/4) > >>

mandrav:

--- Quote from: Vampyre_Dark ---It appears that the CB settings always want to look in the VC++ bin fodler and not the platform SDK folder, even when I set it otherwise. I even add the path to the platform SDK bin in the extra paths options, and it still doesn't work!
--- End quote ---

I now understand the problem. I thought that rc.exe was not ever called.
What C::B version are you using?
1.0-finalbeta had a bug with the compiler extra bin paths, which is fixed in CVS, AFAIK.


--- Quote from: Vampyre_Dark ---I know you didn't delete my post. :)
--- End quote ---

I know you know :). It's just that someone might read it and think otherwise, that's why I had to reply...

Yiannis.

Vampyre_Dark:
This is the link to the cvtres.exe file. You might want to note this somewhere. I can't be the only one to eventually have this problem.
http://download.microsoft.com/download/vstudio97pro/patch/1/win98/en-us/cvtres1.exe

I'm using the finalbeta build.

 :oops: You've made comments about other things I've mentioned being fixed. Maybe I should try the cvs version? Can I just swap out the .exe or do I have to uninstall? I don't want to have to redo all my colours and compiler settings.

Me asking you what you thought of us sending you our custom colours was another thread that was not deleted. :lol:

mandrav:
No need to uninstall :)
But you can't just swap the exe. The plugins need update too and all the zip resource files. You can have more than on C::B version installed at the same time (but they will share configuration settings).
Anyway, it seems that the next release is not too far ahead, so you might want to wait.


--- Quote ---Me asking you what you thought of us sending you our custom colours was another thread that was not deleted.
--- End quote ---

In CVS, there is a new colour configuration system in place. Simple external XML files describe the editor colors for a particular language. To add support for a new language (must be supported by scintilla, mind you), just a new XML file is needed.
Already supported now are:
[*]C/C++ files
[*]RC files
[*]Hitachi H8 assembler files
[*]Lua scripts
[*]GameMonkey scripts[/list:u]
Adding support for other files is just a matter of adding a new XML file and restarting C::B :)
Optionally, a sample file can be added that contains sample code (the one you see when editing the color settings).

Here is the C/C++ lexer
Here is the respective sample file
(if the above links don't work, browse the C::B CVS repository here and navigate to "codeblocks/src/sdk/resources/lexers")

[EDIT]
I 've yet to write documentation about those "magic" index numbers in the lexer files, but I promise I will ;)
[/EDIT]

HTH,
Yiannis.

nfz:
Looks like the "magic" index numbers in the lexer files are the wxStyledTextCtrl Variable Wrappers.

An example is the lua lexxer has an index of 15 which corresponds to wxSTC_LEX_LUA.

Style name "Number" in the lua lexer xml has an index of 4 which corresponds to wxSTC_LUA_NUMBER.

mandrav:

--- Quote from: nfz on October 26, 2005, 02:25:24 am ---Looks like the "magic" index numbers in the lexer files are the wxStyledTextCtrl Variable Wrappers.

An example is the lua lexxer has an index of 15 which corresponds to wxSTC_LEX_LUA.

Style name "Number" in the lua lexer xml has an index of 4 which corresponds to wxSTC_LUA_NUMBER.

--- End quote ---

You can take a look at this message, until a proper document is written.

Navigation

[0] Message Index

[#] Next page

[*] Previous page