You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default behavior of VSTU is to always suggest Unity event functions in the intellisense tool tip.
for example, if I start typing 'up' I will get the Update monobehavior function by default.
However, that is not the case with this plugin. it actually tries to suggest other unity functions/symbols that have 'up' in their name and I personally find this unproductive and it slows me down since I need to always scroll all the way down to the actual Update function.
it would be nice if 'resharper-unity' can give monobehavior event functions highest priority so they always by default in the intellisense tool tip, much like how it is being done in VSTU. In other words, when I start typing 'up' , it should suggest the Update method unless it is already been implemented in the file.
Thanks,
The text was updated successfully, but these errors were encountered:
rob8861
changed the title
suggestion, improve intellisense suugestion for unity monobehavior event functions
suggestion, improve intellisense tooltip for unity monobehavior event functions
Nov 3, 2017
The default behavior of VSTU is to always suggest Unity event functions in the intellisense tool tip.
for example, if I start typing 'up' I will get the Update monobehavior function by default.
However, that is not the case with this plugin. it actually tries to suggest other unity functions/symbols that have 'up' in their name and I personally find this unproductive and it slows me down since I need to always scroll all the way down to the actual Update function.
it would be nice if 'resharper-unity' can give monobehavior event functions highest priority so they always by default in the intellisense tool tip, much like how it is being done in VSTU. In other words, when I start typing 'up' , it should suggest the Update method unless it is already been implemented in the file.
Thanks,
The text was updated successfully, but these errors were encountered: