The 1803 update shouldn’t affect Chrome Intags.
Email me the Voicecomputer log.txt and the settings.ini files.
Nothing obvious in the logs except that it’s not connecting.
"it’d be great if we could remember what changes you made the last time this happened"
My guess is that there’s a conflict with another Chrome extension, most likely a security extension.
Daniel et al.,
The command to "toggle" works fine in Internet Explorer/Firefox because it is designed to refresh InTags by temporarily disabling such so that you can see what's underneath.
However, it isn't designed to work with Google Chrome's "InTag menu" and "InTag window" (i.e., InTag Chrome). Sometimes it will, but that is simply a quirk. What "toggle" is designed to do is to close InTags for short period of time and refresh them so that you can see underneath. It is not designed to switch between the Google Chrome menu bar and the Chrome hyperlinks on a webpage.
Bottom line is that when the menu bar numbered by saying "InTag menu" and you follow it with "toggle", toggle simply refreshes the InTag menu. What you were saying occurs only if InTag menu shuts down the numbers for the menu bar inadvertently because then the InTag Chrome extension takes over, but toggle doesn't do this by design, which is why you get screwy results.
"Life's Rule #1: Once you pull the pin, Mr. Grenade is no longer your friend." (Variant of Murphy's Law - Edward A. Murphy, Jr)Chucker2018-06-07 19:04:03
>But it occurs on chrome pages and Firefox.
But it occurs on chrome pages and Firefox.No numbering on any web page in Chrome or FireFox?Any new Chrome/Firefox extensions?Please send me the VoiceComputer Log.txt file inC:ProgramDataVoiceTeachVoiceComputer