| T O P I C R E V I E W |
| Zeblote |
Posted - Sep 27 2017 : 4:07:27 PM
Most of the time trying to go to an operator definition doesn't work (at least in unreal projects)
The tooltip shows that it knows which overload is interesting here:
However, Alt+G brings up a completely useless list of other operators.
|
| 3 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Sep 28 2017 : 10:47:14 AM
We are working to improve VA's parser, but the IDE intellisense parser works differently to VA's parser. As a result, there are some things that VA understands better, while there are other things that the IDE understands better. Currently this is one of those situations where the IDE is proving more useful. |
| Zeblote |
Posted - Sep 27 2017 : 7:07:11 PM
That works. However, basic "go to definition" in intellisense works totally fine here, so it'd make sense for VA to work aswell... at least only list operators that do something with an FBox instead of everything? |
| feline |
Posted - Sep 27 2017 : 6:36:01 PM
We are aware of some problems with alt-g on overloaded operators, partly because its not always obvious to VA which operator overload is going to be called:
case=1229
If you place the caret into "TotalBounds", on the left hand side of the += and press Alt-Shift-G for the Goto Related menu, the bottom menu item should be "Goto Member..." which will list all of the members of this class, including the overloaded operators. Does this work reliably in your Unreal project? |
