| T O P I C R E V I E W |
| Zeblote |
Posted - Oct 06 2018 : 08:43:05 AM
Appears to be confused by this typedef in an unrelated file:
VA 2291.5, VS 15.8.6 |
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Oct 08 2018 : 06:17:35 AM
All I can really suggest is to keep an eye out and see what happens. This might have been a temporary blip with a parser getting confused. Or it might be something that only happens in a specific file. Unless it can be reproduced on demand its really quite hard to tell or to say. |
| Zeblote |
Posted - Oct 06 2018 : 12:09:21 PM
Hmm not sure what happened there, I just tried it again to look at those fields and now the tooltip is correct. |
| feline |
Posted - Oct 06 2018 : 11:45:55 AM
The context and definition fields are normally shown at the top of the editor window. These are where the Alt-M list appears from, and there is a Go button at the right hand end of the bar. As the caret moves through the file VA updates what is shown in these two fields. Since VA draws these fields, we know this is what VA thinks is going on, and is not what the IDE thinks is going on. |
| Zeblote |
Posted - Oct 06 2018 : 10:20:06 AM
Hmm what do you mean by context and definition fields?
It shows this for go to related:
Alt+g on test does nothing, on TArray takes me to the array template like it should |
| feline |
Posted - Oct 06 2018 : 09:48:26 AM
If you place the caret into this variable name, what does VA show in its context and definition fields? What happens if you press Alt-g?
I am wondering if this is an IDE or a VA tooltip. Just adding a local to a function test with the same type, I am getting a tooltip that is about the local instance, and is nothing to do with the typedef, even when testing inside an Unreal Engine game project. |
