Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 properties in source files improperly underlined?

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
daan.timmer Posted - Feb 03 2011 : 05:31:12 AM
I have a class implementation, something that looks like this:

header:
namespace XpressCommon
{
	namespace Burner
	{
		public ref class Burner abstract
		{
		protected:
			BurnerStatus ^ status;

		public:
			property bool CanPrint
			{
				public: bool get(void);
				internal : void set(bool b);
			}
		}
	}
}


source:
using namespace XpressCommon::Burner;

bool Burner::CanPrint::get(void)
{
	return status->CanPrint;
}

void Burner::CanPrint::set(bool b)
{
	status->CanPrint = b;
}


What happens is that in the header the b in the set(bool b); will be underlined-red
and in the sourcefile the ::set and ::get will be underlined along with CanPrint from status will be underlined.
Within the property body itself it also does not know any members from the class Burner.

Is this a limitation from Visual Studio 2008? Or a problem with Vissual Assist X?

I am running the trial version from VAX to see how I like it, but this quite annoys me to be honest :-)

[edit] screenshot added (I can't upload it to the forums? keeps saying something went wrong?)

5   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Feb 09 2011 : 11:58:29 AM
I am seeing the same effect here. Thank you for the clear description.

case=54976

For now can you try turning on:

VA Options -> Advanced -> Listboxes -> Get content from default Intellisense

this fixes the listbox problem for me, but unfortunately does not help with the underlining. You can turn off the underlining via:

VA Options -> Advanced -> Underlines -> Underline mistyped symbols using

but this will obviously effect all VA underlining of mistyped symbols, and not just in these cases.
daan.timmer Posted - Feb 07 2011 : 1:47:12 PM
I also found a, I guess, bug relating to default accessors.
A generic dictionary accessing through aDictionary[key]-> will not properly list the mejmbers of the returned value.

I will give an example tomorrow when I am back @ work. Currently omw home.

Now just to convince my colleague/employer to get this piece of software :-]


Right, so at work now. I reproduced the bug in a test project, which is totally clean.



I suppose the screenshots describes enough?
feline Posted - Feb 07 2011 : 1:39:03 PM
This is down as a fairly high priority bug, so hopefully this will be looked at fairly soon. Unfortunately I cannot currently give you an estimate, but this thread will be updated when this bug is fixed.
daan.timmer Posted - Feb 07 2011 : 05:25:38 AM
Done that, seems to work indeed. Though it is not our preferred way of coding it will suffice for now.

Will this be something that you @wholetomato will be working on?
feline Posted - Feb 03 2011 : 2:51:26 PM
I am seeing the same effect here. Thank you for the clear description.

case=54796

It looks like this problem is triggered by the:

using namespace XpressCommon::Burner;

line in the cpp file. Can you try commenting this out, and wrapping the cpp file in the namespaces explicitly?

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000