Author |
Topic |
|
Mikademus
New Member
3 Posts |
Posted - Mar 01 2016 : 05:08:39 AM
|
Hi,
I'm evaluating VA for the company I work at. Most everything works excellently but I've run into a showstopper bug:
When selecting an option from the suggestion listbox (tab, enter or mouse doesn't make a difference) the selected symbol is not inserted at the caret position but on a new line on the top of the current document. The caret position is not changed. The only way to get rid of this behaviour seems to be to disable VAssist entirely.
Since the suggestions listbox is an essential tool this renders VAssist useless for the effected developers.
Is this a known bug and is there a fix or workaround?
Thank you, Michael |
|
Mikademus
New Member
3 Posts |
Posted - Mar 01 2016 : 05:23:04 AM
|
The bug is not consistant in that it sometimes/often occurs but not always. FOr me this snippet consitently reproduces the behaviour:
When any option is selected from the listbox that symbol is inserted at the top of the document. Curiously, the focused line retains its position on the screen so some editor compensation for the inserted line is happening. |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Mar 01 2016 : 6:27:39 PM
|
Can you please send in your Visual Studio and Visual Assist settings?
1. IDE tools menu -> Import and Export Settings -> Export selected environment settings 2. VA Options -> Performance -> Export Settings
Would it be possible to send in a file where you can reproduce the problem? Or if the file on your screenshot is from a new test project, it would be even better to zip up and send in the whole project.
You can use the following form to send the files in: http://www.wholetomato.com/support/contact.asp
Please paste the URL of this topic to the "Your request" field, so we can match it up.
What Visual Studio, Visual Assist and Windows versions are you using?
Please go to VAssistX -> Help -> About Visual Assist and press Copy Info, so you can paste it to your email you send via the support form I mentioned above. |
Edited by - accord on Mar 01 2016 6:34:41 PM |
|
|
Mikademus
New Member
3 Posts |
Posted - Mar 22 2016 : 05:09:44 AM
|
VA_X.dll file version 10.9.2089.0 built 2016.02.01 DevEnv.exe version 14.0.24720.0 Professional msenv.dll version 14.0.24720.0 Comctl32.dll version 6.10.10586.0 Windows 10 10.0 Build 10586 4 processors (x86-64, WOW64) Language info: 1252, 0x809
Platform: Project defined Stable Includes: C:\Program Files (x86)\Windows Kits\8.1\Include\winrt; C:\Program Files (x86)\Windows Kits\8.1\Include\shared; C:\Program Files (x86)\Windows Kits\8.1\Include\um; C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include;
Other Includes:
Stable Source Directories: C:\Program Files (x86)\Windows Kits\10\Source\10.0.10240.0\ucrt; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\crt\src; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\atl; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\mfcm; C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\mfc;
|
|
|
feline
Whole Tomato Software
United Kingdom
19014 Posts |
Posted - Mar 22 2016 : 2:09:31 PM
|
Thank you for the update. Does installing VA 2093, which we have just released, make any difference to your problem?
http://www.wholetomato.com/downloads/default.asp
Since you have a code snippet that always produces this problem, are you able to reproduce this problem on demand in a new, test project you might be able to send us? This would help us to test this, and to try to figure out what is going wrong here. |
zen is the art of being at one with the two'ness |
|
|
|
Topic |
|