| Author |
 Topic  |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
 Posted - Apr 08 2008 : 2:52:08 PM
|
You are working on coloring, so it maybe a good time to report a coloring issue. 
"#pragma" and the words after it is coloring by Visual Studio in the editor (so VA do not need to overwrite it). But everywhere else VAX is need to decide it's color (for example in VA View).
- #pragma is colored blue by default (keyword color) both in VA View and Editor.
- #pragma keywords (once, warning, etc.) is colored as keywords in editor (blue by default), but VA is coloring it as a variable (VA Fonts and Colors).
- non-keyword words colored as an identifier in the editor (Fonts and Colors in options dialog of the IDE, black by default), VA is using variable color.
For example #pragma once is blue in the editor, but VA is using variable color for "once". |
Edited by - accord on Apr 08 2008 5:35:34 PM |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Apr 08 2008 : 5:42:39 PM
|
After other stuffs like #ifdef should also use IDE identifier color (default: black) instead of VA variable color.
If someone (like me) using a bright color for VA variable color, the difference will be a huge  |
Edited by - accord on Apr 08 2008 5:45:43 PM |
 |
|
|
feline
Whole Tomato Software
United Kingdom
18942 Posts |
Posted - Apr 10 2008 : 3:49:44 PM
|
Do you have some examples? The only thing I ever use #pragma for is #pragma once
I see the colouring problem with "once" on the #pragma line.
#ifdef, this is being coloured as a keyword for me in VA Outline.
In your second post, do you mean that:
#define CHOCOLATE_CAKE 1
#ifdef CHOCOLATE_CAKE
should colour the second instance of "CHOCOLATE_CAKE" as a variable in VA Outline? Surely it should be coloured as a macro?
Or are you talking about words after #ifdef that VA does not recognise? |
zen is the art of being at one with the two'ness |
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Apr 13 2008 : 12:22:38 PM
|
>Or are you talking about words after #ifdef that VA does not recognise?
Yes, sure. For example:
//#define CHOCOLATE_CAKE 1
#ifdef CHOCOLATE_CAKE
Notice the // before the first line
So, first of all, VAX should use identifier color instead of it's own variable color for default color.
(Identifiers are black by default, variables are gray by default.)
#pragma keywords are less important, but an example:
#pragma warning( disable : 4244 )
should colored like in the IDE instead of like this
#pragma warning( disable : 4244 )
(Brown is used to represent the variable color)
Strange: VAX is already using the right color for parenthesis and numbers...
So, the rule is simple: every place where VAX cannot identify a symbol should use IDE identifier color, instead of VA variable color. |
Edited by - accord on Apr 13 2008 12:36:20 PM |
|
|
| |
Topic |
|
1632: #pragma coloring
