Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Syntax highlighting invalid

(1/2) > >>

Loaden:

--- Code: ---    SetProcessWorkingSetSize(GetCurrentProcess(), -1, -1); // valid
#ifdef __WXMSW_
    SetProcessWorkingSetSize(GetCurrentProcess(), -1, -1); // invalid
#endif
--- End code ---

MortenMacFly:

--- Quote from: Loaden on September 18, 2010, 12:38:28 pm ---

--- End quote ---
This is not invalid, but a new feature of scinitilla (and already reported in the forums). However, we should make this an option.

Loaden:
I see, but why not change color from black to grey?
It is possable?


--- Code: ---#if 0
int grey() {} // Because have not syntax highlighting, so make the corlor from black to grey?
#else
void black();
#endif
--- End code ---

MortenMacFly:

--- Quote from: Loaden on September 20, 2010, 01:57:46 am ---I see, but why not change color from black to grey?
It is possable?

--- End quote ---
I think so, yes.

oBFusCATed:
Morten: do you feed the scintilla with the correct list of defines for the edited file?
If not please disable this feature for now, because it is useless...

Also, what happens if I open file that is not part of a project or it is part of a Makefile project?
I think both should have this automatically disabled...

Another thing: does scintilla open include files? What will happen if I've got:

--- Code: ---// a.h
#define A_TEST

// a.cpp
#include "a.h"

#ifdef A_TEST
    .... code1 ....
#else
    .... code2 ....
#endif

--- End code ---
Which of the two will be highlighted and which won't?

Navigation

[0] Message Index

[#] Next page