[enhancement] editor option to avoid faded color on not recognised switch

[GoogleCodeExporter]

My concern is more an enhancement than an issue.
I'm using seascope to navigate through kernel sources. My problem is that since 
the switch are not defined in a file within the source code tree, seascope put 
the sections which are under unrecognized switch in grey or faded color.

Could it be possible to have an option to deactivate this behavior?

I was using version 0.6 before, and it did not have this feature. I only saw it 
on 0.7.

What version of the product are you using? On what operating system?
0.7 Ubuntu 12.04

Please provide any additional information below.

Original issue reported on code.google.com by evilo79....@gmail.com on 27 Feb 2013 at 8:30

[GoogleCodeExporter]

Can you please send me a file to test the same ?
When you say switch, did you mean switch statement of C or the function 
pointers ?
Where are they faded ? Inside editor ? Inside ctags view ?
Even a screenshot would be great to understand issue.

Original comment by anil.om...@gmail.com on 27 Feb 2013 at 6:17

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Here is a screenshot of the problem I'm talking about.
I'm using seascope to browse linux kernel sources (c language), and I'm talking 
about a "#ifdef" switch.

As you may be able to see in the attached image, in the editor the code after 
the line "#ifdef __KERNEL__" is displayed in faded color. 

Hope it'll help.

Original comment by evilo79....@gmail.com on 28 Feb 2013 at 5:21

Attachments:

• seascope_fadedcolor.jpg
• stm.h

[GoogleCodeExporter]

I tried seascope on linux kernel and i see that code under #ifdef __KERNEL__ 
was not faded.

Any specific file in linux kernel which consistently reproduces this issue ?
Does it happen with all files having __KERNEL__ ?
which version of python-qt4, python-qscintilla2 are you using ?
I don't do anything magical w.r.t. syntax highlighting, i just rely on 
qscintilla to do the same

Original comment by anil.om...@gmail.com on 3 Mar 2013 at 3:00

[GoogleCodeExporter]

I am able to reproduce this issue in debian sid, let me see what changed 
between seascope 0.6 and seascope 0.7

Original comment by anil.om...@gmail.com on 3 Mar 2013 at 3:22

[GoogleCodeExporter]

Recent qscintilla has preprocessor tracking enabled by default. Check 
http://www.scintilla.org/nulex.html for description of this feature.
Code for same is at 
https://github.com/Open-Turing-Project/turing-editor-qt/blob/master/QScintilla/l
exers/LexCPP.cpp#L260

I have updated seascope to set property "lexer.cpp.track.preprocessor" to "0".
Please use the latest repository code for the fix.

Original comment by anil.om...@gmail.com on 4 Mar 2013 at 9:00

• Changed state: Fixed

[GoogleCodeExporter]

Works well.
Thx.

Original comment by evilo79....@gmail.com on 4 Mar 2013 at 12:54