| Author |
 Topic  |
|
|
rachelkim12
New Member
4 Posts |
 Posted - Nov 20 2017 : 7:13:12 PM
|
Hi,
I have a problem with using VA. I'm not sure when it's started, but I can't use full VA such as shortcuts (open files in solution, go to the implementation, etc).
Also, only three icons are activated.
What I did to fix this are...
1. Disable -> Enable VA
2. Reinstall VA
Both were not working for me.
How to fix this?
Thanks
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Nov 21 2017 : 07:33:43 AM
|
Are you able to open the VA Options dialog?
Which IDE and version of VA are you using?
Do you have a solution open in the IDE when this is happening? Do you have any code files open in the IDE? What programming language is your solution using?
What happens when you press the 2nd or 3rd icons on the VA toolbar? They are shown as enabled in your screen shot, and these are the buttons for the Open File and Find Symbol dialogs. |
zen is the art of being at one with the two'ness |
 |
|
|
rachelkim12
New Member
4 Posts |
Posted - Nov 26 2017 : 11:40:49 PM
|
Are you able to open the VA Options dialog?
- Yes, I am able to open it
Which IDE and version of VA are you using?
- I'm using visual studio 2017 enterprise and VA version is 10.9.2238.2.
Do you have a solution open in the IDE when this is happening?
- Yes I have
Do you have any code files open in the IDE?
- Yes I have
What programming language is your solution using?
- C++
|
|
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Nov 27 2017 : 12:06:11 PM
|
We got the same report from a different user a while ago, and it was caused by Windows 10's Fall Creators Update. What Windows version are you using? You can see the build number at
VAssistX -> Help -> About
after "Windows 10 10.0 Build "
> I'm not sure when it's started
A Windows Update may be reason why it started unexpectedly, since I wouldn't think that the two are related. |
Edited by - accord on Nov 27 2017 12:17:25 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Nov 27 2017 : 1:29:30 PM
|
If you go into the VA options dialog, do you have:
VA Options -> Display -> Display VA Navigation Bar:
turned On or Off? By default, this is turned On.
When you open a .cpp file, is the navigation bar showing? Is there a "hole" where the navigation bar should be? The "hole" can happen if you are seeing the problem related to the Windows 10 Fall Creators Update. |
zen is the art of being at one with the two'ness |
|
|
|
rachelkim12
New Member
4 Posts |
Posted - Nov 27 2017 : 1:39:28 PM
|
Hi accord,
My Windows 10 version is 10.0 Build 16299
Thanks :)
quote:
Originally posted by accord
We got the same report from a different user a while ago, and it was caused by Windows 10's Fall Creators Update. What Windows version are you using? You can see the build number at
VAssistX -> Help -> About
after "Windows 10 10.0 Build "
> I'm not sure when it's started
A Windows Update may be reason why it started unexpectedly, since I wouldn't think that the two are related.
|
|
|
|
rachelkim12
New Member
4 Posts |
Posted - Nov 27 2017 : 1:43:58 PM
|
Hi feline,
It was turned on. And I didn't see any holes in there.
Hmmm It's interesting. Suddenly visual assist is working well.
What I did was like this.
1. Turned off navigation bar
2. Restart VS2017
3. Turned on navigation bar
If I meet the same issue again, I will contact this forum again.
Thanks :)
quote:
Originally posted by feline
If you go into the VA options dialog, do you have:
VA Options -> Display -> Display VA Navigation Bar:
turned On or Off? By default, this is turned On.
When you open a .cpp file, is the navigation bar showing? Is there a "hole" where the navigation bar should be? The "hole" can happen if you are seeing the problem related to the Windows 10 Fall Creators Update.
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Nov 27 2017 : 2:28:28 PM
|
You do have Windows Fall Creators Update installed, from your Windows build number. But what you are seeing is not the problem that we were thinking about.
I have no idea what went wrong here, or why this fixed it. It almost sounds like something in the IDE changed, stopping VA from fully loading. But normally when this happens VA is more fully disabled, and you cannot get into the VA options dialog.
Thank you for the update, I am very glad this is now fixed and working properly for you.
If you encounter another odd problem with VA, it might be worth going into the:
IDE tools menu -> Extensions and Updates...
dialog, locate VA in the list of installed extensions, and disable VA. This will require an IDE restart. After the restart, go back into this dialog and enable VA, with another IDE restart. If the problem is related to an IDE update, then this may fix it. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Suddenly VA is not working on VS2017
