Visual Assist includes parsers that execute after each pause in typing. To avoid any chance of lag between your initiating a command and its response, the parsers do not activate until your pause exceeds a threshold. Visual Assist wants your IDE to be responsive.
Unfortunately, the tiny delay means there are a few occasions whereby you can request a command that is not yet available. Such commands:
- appear in the Quick Action and Refactoring menu (Shift+Alt+Q)
- appear in the the IDE context menu (Right-click)
- initiate Smart Select
For example, expecting Create from Usage before a reparse can see a newly typed symbol means the command will not appear in the Quick Refactoring Menu.
If a command you expect is unavailable, clear its access menu (if applicable,) wait one second, and retry the command.
Alternatively, you can make Visual Assist always reparse between your initiating a command and seeing a response by modifying the registry:
HKCU\Software\Whole Tomato\Visual Assist X\<IDE spec>\ReparseIfNeededMaxFileSize2
Set to -1 to reparse if necessary, irrespective of file size.
Set to 0 to reparse only after a delay in typing.
Set to a value in bytes to reparse if necessary in files whose size is smaller than or equal to the value.
Set to 0 to restore the default.
Visual Assist build 2093 through build 2101
Registry value name is ReparseIfNeededMaxFileSize and its default data is 20,000, meaning a reparse is always done between a command and its response—if necessary—in files of 20,000 or fewer bytes.
Visual Assist build 2089 and older
ReparseIfNeededMaxFileSize is not recognized.
|Resolve a performance problem with Visual Assist||Starting point for all performance problems|