User forums > Using Code::Blocks
Resources
kkez:
--- Quote from: TDragon on February 05, 2006, 04:51:03 pm ---Unfortunately I've never come across a good reference for the structure of a .rc file (maybe someone else can chime in here?);
--- End quote ---
Resource definition statement.
Oh, hi Decrius :P
kkez:
btw, my .rc file no longer have the syntax highlighting even if the filemask for the lexer is .rc... (bug?)
Now, if i change the highlight mode in the edit menu, all the [ + ] to unfold the blocks of code disappear even if the line count remains the same. I just can't unfold it again :( (bug?)
EDIT: wait, all the lexers switched by one from the D lexers: the D lexer has the fortran77 filemask and so on... better go look inside the default.conf file...
takeshimiya:
--- Quote from: kkez on February 05, 2006, 06:00:54 pm ---btw, my .rc file no longer have the syntax highlighting even if the filemask for the lexer is .rc... (bug?)
Now, if i change the highlight mode in the edit menu, all the [ + ] to unfold the blocks of code disappear even if the line count remains the same. I just can't unfold it again :( (bug?)
EDIT: wait, all the lexers switched by one from the D lexers: the D lexer has the fortran77 filemask and so on... better go look inside the default.conf file...
--- End quote ---
That's a bug: the lexers are indexed by IDs.
kkez:
everything is fine now, i just deleted everything between <color_sets> and </color_sets>. Maybe in the previous revision the lexers were read in the order they are and my conf file still had the old list...
takeshimiya:
--- Quote from: kkez on February 06, 2006, 12:12:04 pm ---everything is fine now, i just deleted everything between <color_sets> and </color_sets>. Maybe in the previous revision the lexers were read in the order they are and my conf file still had the old list...
--- End quote ---
Yes, that's because they're being indexed by IDs, which will screw up all the lexers when a new lexer get's added. :)
Navigation
[0] Message Index
[*] Previous page
Go to full version