Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 New VAssist eats next word. Again.
 New Topic  Reply to Topic
 Printer Friendly
Previous Page
Author Previous Topic Topic Next Topic
Page: of 3

eddieparker
Senior Member

39 Posts

Posted - Aug 14 2018 :  09:41:32 AM  Show Profile  Reply with Quote
Just adding my two cents: this feature is sort of tribal knowledge around my workplace and people tend to write to me to remember which cryptic registry key they need to set after they hear about it from someone else, or their machine gets reinstalled, etc.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
16614 Posts

Posted - Aug 14 2018 :  12:38:34 PM  Show Profile  Reply with Quote
Mordachai, all of the current registry keys are listed and explained here:

https://docs.wholetomato.com/default.asp?W795

which also helps to explain why we are not rushing to put all of them into our options dialog, it would add quite a lot of options that most people, most of the time, don't want to change. But it does seem that this specific setting is being used more than I had realised.

The specific request for adding this setting to our options dialog is:

case=102623

one reason for not rushing to add this setting to the options dialog is that this change only works in C/C++, not C#. Also, it is not heavily tested, and we know that sometimes it does not work quite as expected.

How widely is this being used in your companies?

As for the more general question of what to do when your machine gets re-installed, sadly, I have resorted to keeping a record of all of the different settings I need to configure in the software I rely on, so that I can get things back to working correctly when I have to move to a different machine or reinstall. It feels like there should be a better solution, but across so many different programs, and different options, I am never going to remember all the useful changes I have found and made.

zen is the art of being at one with the two'ness
Go to Top of Page

eddieparker
Senior Member

39 Posts

Posted - Aug 14 2018 :  2:17:51 PM  Show Profile  Reply with Quote
I don't know the number of people that actually use the settings, but when I send out a mail telling people about the setting, I tend to get hordes of replies thanking me for solving an annoyance they have. Inevitably they forget it, have another machine, reformat, etc, and then they come and ask me for the setting again.

Does VAssist not do any telemetry? It might be neat to see how many people in the wild have certain settings enabled or regkeys on. Although the discoverability of the regkeys might not make any statistics you get super useful.

Lastly, I've never written a visual studio plugin, so salt my question appropriately: can't Visual Studio synchronize your settings via it's roaming profile stuff? I'm not sure how hard/easy that is, but that'd be nice for these sorts of settings.

Thanks again for taking the feedback. I do wish there was an easier UI for this, even if it was buried under an "Advanced/Experimental/These-Might-Change" fold-out.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
16614 Posts

Posted - Aug 14 2018 :  2:52:43 PM  Show Profile  Reply with Quote
We do collect some high level telemetry, but nothing this detailed. We are considering a page for the registry key settings, but don't want to cause more problems than we solve.

As for exporting VA settings more easily, this is something we are considering:

case=79188

zen is the art of being at one with the two'ness
Go to Top of Page

Mordachai
Tomato Guru

USA
224 Posts

Posted - Aug 15 2018 :  2:54:11 PM  Show Profile  Reply with Quote
To get on my personal soap-box for a moment:

Windows & MS got it wrong. Badly, deeply, deplorably, regrettably, foolishly, wrong; from the beginning.

The registry is and was and remains a TERRIBLE place to store software-configuration information that is truly related to the user, and not the per-machine instance system wide settings. Those make sense in the registry, and should not normally be user-editable, and should not normally be something one would want to migrate to any other machine. They should be - machine specific settings and configuration data for applications and the OS.

User configuration information should ALWAYS have been stored in the USER's space - visibly - in a simple text editable file format that migrates with the user (and for per-user but machine-specific configuration data, well, probably the registry is fine - that would need to be carefully considered on a case-by-case basis).

When MS moved from .ini files to the registry - they were deeply foolish to not simply insist that .ini be stored in user space, and system settings in reg space. Ah well. Stupidity rules the planet, for the most part.
Go to Top of Page

Mordachai
Tomato Guru

USA
224 Posts

Posted - Aug 15 2018 :  3:01:12 PM  Show Profile  Reply with Quote
As to your specific questions / answers:

At my work, there is exactly one developer who uses VA at all - me. And I am 50% of the C++ development force here. The other dev is an old-school C developer, and things like classes and namespaces and the intricacies of templates or even of smart-pointers and the like - are only understood so well, and only used to a certain extent. So having a tool like VA which helps manage the complexity of the more sophisticated applications of C++ language are not of interest. In fact, I believe he uses Notepad++ as his preferred source editor, and the syntax highlighting available there is all he desires.

If I worked at a larger organization? Who knows? It is my anecdotal experience that most software engineers aren't into C++, most software houses do not use C++, and even those who do largely are skittish about what new language features they allow their devs to incorporate - still largely insisting on something akin to C++ 98 or even prior to that.

I have the great pleasure to choose my own tools, and VA has been an integral part of our success here since I started using your product - over a decade ago - maybe much longer? I lose track of time.

For my 2c - I would very much wish to encourage case=79188 - even if this registry setting is never made into a top-level configuration option - being able to export and later import my user-settings (or better, take my rant about user-settings to heart and move this and all other user-settings out of the registry and into my user account's documents\VAX\ folder or something similar).

It is - mildly insane - that any modern software cannot trivially be reinstalled or moved to a new machine - along with all of my customizations of it - seamlessly.

case=79188

Please!

Edited by - Mordachai on Aug 15 2018 3:03:43 PM
Go to Top of Page

Steve Carlisle
Starting Member

USA
1 Posts

Posted - May 14 2020 :  8:01:54 PM  Show Profile  Reply with Quote
This really does need to be added to the GUI, and it should take this much teeth pulling to get it there.

I am using VAssistX in Atmel Studio. Unsurprisingly, there is no existing entry in my registry that has what could be clearly seen to be a <IDE Spec> for Atmel Studio, and there's nothing in your list of acceptable <IDE Spec>s for it. So right off the bat, I'm left to hack at it. Not cool.

Secondly, it is not clear from your "article" on modifying the registry how exactly it should be entered. Is it added as a Key or a DWORD or something else. If its a Key, and I supposed to set the default value for the key. Why not be explicit about this. I don't want to hack at your options and play a guessing game on why it's not working.

There's just no reason for this kind of confusion y'all. Make it an option in the GUI and be done with it. All this nonsense for such bad default behaviour and poorly documented "solution" is infuriating.
Go to Top of Page

eddieparker
Senior Member

39 Posts

Posted - May 14 2020 :  9:02:28 PM  Show Profile  Reply with Quote
I agree with you Steve. I can understand that for Whole Tomato this setting is a default and changing a default might be bad, but it is unfortunate that this destructive behaviour is the default, and not easily fixed without the registry setting.

If it helps, I keep a regkey on my DropBox with these contents, so I can apply it on new machines:
quote:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Whole Tomato\Visual Assist X\VANet15]
"CompletionOverwriteBehavior"=dword:00000001
[HKEY_CURRENT_USER\Software\Whole Tomato\Visual Assist X\VANet14]
"CompletionOverwriteBehavior"=dword:00000001
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
16614 Posts

Posted - May 15 2020 :  10:40:43 AM  Show Profile  Reply with Quote
Apologies for not having Atmel registry keys listed in the documentation, I am adding them now.

eddieparker, these are the keys for Visual Studio. For Atmel the values and types are the same, but the keys are stored in a different place in the registry.

Steve, you want to close Atmel and then edit:

HKEY_CURRENT_USER\Software\Atmel\Whole Tomato\Visual Assist X\AtmelStudio7\CompletionOverwriteBehavior

This key already exists on my Atmel system, so I would expect it to already exist on your system as well. It is type is DWORD (32-bit) Value.

zen is the art of being at one with the two'ness
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
16614 Posts

Posted - May 15 2020 :  10:44:09 AM  Show Profile  Reply with Quote
We are also aware that making these settings more available would be helpful, but want to do this without overwhelming our options dialog:

case=69399

zen is the art of being at one with the two'ness
Go to Top of Page
Page: of 3 Previous Topic Topic Next Topic  
Previous Page
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000