| Author |
 Topic  |
|
|
Uniwares
Tomato Guru
Portugal
2322 Posts |
 Posted - Sep 24 2005 : 8:30:03 PM
|
Would be nice when at least two of the windows could agree how to color the words "virtual", "void" and "Setup". sigh...
 |
Edited by - Uniwares on Sep 24 2005 8:37:46 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Sep 25 2005 : 08:35:43 AM
|
i remember spotting this myself 
case=145 |
zen is the art of being at one with the two'ness |
 |
|
|
bugfix
Tomato Guru
Germany
324 Posts |
Posted - Sep 28 2005 : 02:23:54 AM
|
here we go again... *sigh*
only first entry of array is colored right.
foo param Color is colored as type.
foo param ParamBlock is colored as type.
variable of ctors init list is colored as foo.
vs2k3, c++, 1423
will you get new parser ever stable?:) |
http://www.mf-sd.de |
|
|
|
bugfix
Tomato Guru
Germany
324 Posts |
|
|
Uniwares
Tomato Guru
Portugal
2322 Posts |
Posted - Sep 28 2005 : 09:09:57 AM
|
let me add one more... AND EXPLAIN ME THAT! All of the case labels are enums, actually defined in the same enum block.
 |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Sep 28 2005 : 2:47:43 PM
|
Uniwares:
We are unable to repro the problem with virtual. We suspect your use of it (who knows where??) is confusing our parser into thinking you've defined a symbol called virtual. Unfortunately, "int virtual;" isn't enough to confuse our parser -- virtual remains blue in our simple test. Any chance you can find the culprit?
In the cases with "D3DFILL_WIREFRAME" and "case hdr_leon_from", we suspect VA X sees (or believes it sees,) multiple definitions for these symbols. Do such definitions exist? If not, can you provide sample code with the definitions so we can see how they might be confusing our parser?
Variables constructors being colored like functions, and "D3DLIGHT9 *Light" being colored blue, are reproducible and probably fixable within the constraints of our architecture. They are on our list. |
|
|
|
bugfix
Tomato Guru
Germany
324 Posts |
Posted - Sep 28 2005 : 3:23:09 PM
|
from d3d9types.h
typedef enum _D3DFILLMODE {
D3DFILL_POINT = 1,
D3DFILL_WIREFRAME = 2,
D3DFILL_SOLID = 3,
D3DFILL_FORCE_DWORD = 0x7fffffff, /* force 32-bit size enum */
} D3DFILLMODE;
Anyways, here is a small repro that confuses VAX.
enum eBlub
{
eBlub_A, eBlub_B, eBlub_C
};
eBlub table[3] =
{
eBlub_B, eBlub_C, eBlub_A
};
Using 1424 now. |
http://www.mf-sd.de |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Sep 28 2005 : 3:29:50 PM
|
bugfix i have reproduced the problem in your array of enum's screen shot
case=789
support have covered your screen shot labelled "variable of ctors init list is colored as foo."
i cannot reproduce any of the other effects here. i have typed in the code blocks as shown, and while lots of things are underlined the problems are not showing up.
Uniwares i cannot reproduce yours either. enum's seem less likely to be redefined, so i don't know what to make of this.
is anyone able to post a code snippet that reproduces these problems on its own? i suspect these are context sensitive problems *sigh* |
zen is the art of being at one with the two'ness |
Edited by - feline on Sep 28 2005 3:32:56 PM |
|
|
|
bugfix
Tomato Guru
Germany
324 Posts |
Posted - Sep 28 2005 : 3:38:47 PM
|
After installing 1424 both Color and ParamBlock thing are now colored ok.
Still Light->Type is shown wrong. If I simply enter "Type a;" VAX points to "class System.Type : System.Reflection.MemberInfo" although its a pure c++ project.
|
http://www.mf-sd.de |
|
|
|
Uniwares
Tomato Guru
Portugal
2322 Posts |
Posted - Sep 28 2005 : 4:42:53 PM
|
quote:
Originally posted by support
Uniwares:
We are unable to repro the problem with virtual. We suspect your use of it (who knows where??) is confusing our parser into thinking you've defined a symbol called virtual. Unfortunately, "int virtual;" isn't enough to confuse our parser -- virtual remains blue in our simple test. Any chance you can find the culprit?
The only thing I can see is that the class defines AND declares the function.
class CLogIP : public CLogBase
{
...
protected:
virtual void Setup()
{ ... some code here
}
};
quote:
In the cases with "D3DFILL_WIREFRAME" and "case hdr_leon_from", we suspect VA X sees (or believes it sees,) multiple definitions for these symbols. Do such definitions exist? If not, can you provide sample code with the definitions so we can see how they might be confusing our parser?
No multiple definitions (besides of having multiple (vss-shared) files). See the following shot, which is taken right from the beginning of the header file which defines those enums. Note the #define too.
Thats all that is to that code.
Am going to try the new build now. Lets see. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Sep 29 2005 : 3:12:04 PM
|
bugfix i have reproduced the problem with Type.
case=793
if Type is defined in a stable C++ header then this definition is used for preference. on my development machine it shows as being the enum
QApplication::Type
from Qt. this goes to support the idea that VA is finding multiple definitions of some symbols, and thus getting confused. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Sep 29 2005 : 3:23:06 PM
|
Uniwares, in the virtual screen shot are the colours of "virtual" and "void" defined as anything? using the slightly expanded code:
class CLogIP : public CLogBase
{
private:
long m_ipNumber;
bool m_known;
protected:
virtual void Setup()
{
m_ipNumber = 0;
m_known = false;
}
};
both virtual and void are shown in the same colour here.
after having typed in the first 10 lines of your #define and enum screen shot the colouring is all fine here. from memory you develop under both windows and UNIX. grasping at straws here, but is this header file UNIX format? or perhaps a mix of windows and UNIX format line endings? |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Oct 12 2005 : 7:30:46 PM
|
the original case was rather specific, so lets have a new case for the definition field colouring.
case=830 |
zen is the art of being at one with the two'ness |
|
|
|
Uniwares
Tomato Guru
Portugal
2322 Posts |
Posted - Oct 12 2005 : 7:49:12 PM
|
| 1426 solved that problem after cleaning the db, cache etc. Although I still see lots of odd colored symbols all around. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Oct 13 2005 : 3:14:13 PM
|
| support are hoping that the hyper threading fix will help with these odd colouring problems. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Topic Locked
