#include <iostream>


class MyClass
{
public:
	MyClass();
	~MyClass();
	void getInt();
private:

};

MyClass::MyClass()
{
}

MyClass::~MyClass()
{
}

void MyClass::getInt()
{
}

int main() {


	auto intPtr = std::make_unique<MyClass>();

	intPtr->getInt();
}

quote:

---

Originally posted by feline

If you only work with a single solution, then just making this file once will be enough. Since VA always looks for the file when rebuilding its symbol database, the file will always take effect.

If however you work with a range of different solutions, and want this to apply to all of them, which would make sense, since it looks like its the specific version of the STD header file that is confusing VA, place the "va_stdafx.h" file into the directory:

%APPDATA%\VisualAssist\Misc
so you get:

%APPDATA%\VisualAssist\Misc\va_stdafx.h

but do remember that this file will be applied to ALL solutions you open on this machine, since sometimes you want solution specific edits in va_stdafx.h

---

quote:

---

Originally posted by feline

I believe the problem is that you are using a slightly different version of the Windows SDK to me, which has a different definition of make_unique, that somehow is confusing our parser. So VA doesn't properly understand make_unique and make_shared on your system, even though it does on mine.

So, can you please navigate to the folder holding your SLN file, and in this folder create a new, empty text file called "va_stdafx.h", then edit it to have the content:

namespace std {
template <class _Ty>
	unique_ptr<_Ty> make_unique(_Types&&... _Args);
	
	template <class _Ty>
	shared_ptr<_Ty> make_shared(_Types&&... _Args);
};

making sure there is a blank line at the end of the file. Now press the button:

VA Options -> Performance -> Rebuild symbol databases

and restart Visual Studio.

When rebuilding its symbol database VA looks for this file, and if found, it parses it before parsing anything else in your solution. Since we look for this file specifically, there is no need to add it to your solution, and in fact it should not be added to your solution, but it should be safe to check it into source control if you want.

This file is used to help our parser make sense of any odd code that it might encounter, especially macros that might cause us problems. In this situation I am using it to make sure that VA understands the return type of these two functions. This has fixed the problem in the test solution you sent me, and I suspect it will work well with your main solution as well.

---

namespace std {
template <class _Ty>
	unique_ptr<_Ty> make_unique(_Types&&... _Args);
	
	template <class _Ty>
	shared_ptr<_Ty> make_shared(_Types&&... _Args);
};

quote:

---

Originally posted by feline

Thank you for the update, I am glad that something has been fixed, at least.

Since you are now using VA 2535 you may want to turn Off:

VA Options -> Display -> Display VA Navigation Bar:

since this version of VA contains a known bug, where the IDE quick find dialog, CTRL-F, looses focus as you are typing in a string to find. Disabling the VA navigation bar is a reliable work around for now, until we can get a fix released for this problem.


Hello, i tried making a new c++ console application, and empty project, i still have the same issue smart pointers would not work. I have reinstalled and reset visual studio settings but it still didn't fix it.



For the stl pointers though, I am wondering if this is somehow a solution specific problem.

If you have the time, can you please try making a new, default C++ solution inside Visual Studio. So nothing involving Unreal Engine. Do you still see the problem there? If this works correctly this would explain why so far I haven't been able to reproduce this here, even with the clear sample code.

---

quote:

---

Originally posted by feline

Do you have:

VA Options -> Editor -> Convert dot to -> in C/C++

turned On?

If you use Alt-Shift-G on "localTPtr" and look at "Types of Symbol", what do you see? Testing in UE 5.3, I have 2 sub-items, which are:

TObjectPtr<simpleDateTypeForPointer>
> simpleDateTypeForPointer


and if you instead select "Goto member..." in the menu, you should get a dialog showing the members of TObjectPtr<simpleDateTYpeForPointer> which holds 48 items, including an operator->

How does this compare to what you are seeing?

---

quote:

---

Originally posted by feline

Thank you for the details. This suggests VA isn't working out the return type of "std::make_unique" as you have probably worked out. I am aware we have run into some problems with "std::make_unique" before, but the problem with TObjectPtr is a completely new one for me.

I am looking into the make_unique and make_shared problem now.


For "TObjectPtr", using VS2022, VA 2530 and UE 5.2, I have set up the following very simple test case. In a header file I have the following struct:

struct simpleDateTypeForPointer
{
	short nCharHeight;
	short nCharWeight;
	bool bWearingHat;
	bool bCarryingSword;
};

and in the cpp file I am using it like this:

	TObjectPtr<simpleDateTypeForPointer> localTPtr;
	localTPtr;

typing the dot after "localTPtr", the dot is automatically converted to -> for me, and I automatically get a listbox appear.

I have just tried disabling IDE intellisense via:

IDE tools menu -> Options -> Text Editor -> C/C++ -> Advanced -> Disable Database = True

and restarting VS2022. No change in how VA handles this code. A quite Find in Files for TObjectPtr is showing plenty of usage like this, suggesting this is reasonable code to write. But is this what you are doing in UE? If so, which version of UE are you using?

---

struct simpleDateTypeForPointer
{
	short nCharHeight;
	short nCharWeight;
	bool bWearingHat;
	bool bCarryingSword;
};

	TObjectPtr<simpleDateTypeForPointer> localTPtr;
	localTPtr;

quote:

---

Originally posted by feline

Odd. I am seeing the same effect here, and trying to understand why. So far it seems to be limited to std::make_unique which is something.

Does a valid listbox appear when you press CTRL-SPACE? It does for me.

---