Author Topic: Syntax highlighting in between #ifdef prepocessor statements  (Read 5704 times)

Offline secks

  • Multiple posting newcomer
  • *
  • Posts: 20
Syntax highlighting in between #ifdef prepocessor statements
« on: September 16, 2010, 08:57:38 pm »
I just updated to svn 6595 - Sept 15 2010 11:04:41 - linux, from jenslody and now all code (C++) in between conditional proprocessor commands' syntax highlight is gone .. all code is black .. does anyone know of a setting to disable that?  It's quite annoying and is new to my build .. I can't find any options in settings anywhere about it ..

Example

Code
//this code has normal highlighting
int a;
a = 1;
if(a == 1) {
  #ifdef FAKEDEFINE
    //this code is all black
    cout << "WHY DONT I HAVE COLOR!!!???" << endl;
 #endif
 //back to normal color
  cout << "I have color here though :)" << endl;
}

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5502
Re: Syntax highlighting in between #ifdef prepocessor statements
« Reply #1 on: September 16, 2010, 09:29:45 pm »
I have noticed this too an hour ago. Could this be related to the wxscintilla upgrade ?

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Syntax highlighting in between #ifdef prepocessor statements
« Reply #2 on: September 16, 2010, 10:03:34 pm »
I have noticed this too an hour ago. Could this be related to the wxscintilla upgrade ?
Yes! That's one of the new features: Scointilla scans the files for #defines and "greys" what's not relevant.
However, probably we should make this an option.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline secks

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: Syntax highlighting in between #ifdef prepocessor statements
« Reply #3 on: September 17, 2010, 01:27:01 am »
Yes! That's one of the new features: Scointilla scans the files for #defines and "greys" what's not relevant.
However, probably we should make this an option.
It's actually greying out code that will be included from a preprocessor define though .. An option would definitely be nice .. If I had free time I'd look into it but unfortunately I don't at the moment :( ..