A new release is available. You can download it by following the link that you received with your order.
The current version of the VoiceComputer Chrome extension is 6.25. It should get automatically updated.
Ron may be able to answer your question a little better, but as far as I know I don't see anywhere where you can change the font color in the Chrome extension.
The font color for the Chrome Intags can’t be changed at this time BUT you can change the Opacity of the Intags by clicking on the Intag logo on the top right corner of Chrome. By doing this, you should be able to change the contrast so that the Intags are easily visible.
Ron, is there anything in particular you would like us to test
I’ve installed and configured the new version
We’re looking at 3 occasional bugs that are rare enough that we haven’t been able to gather enough information to have a chance of fixing.
I’ll let you know Ron but I’m probably not the right person to test this.
I’ve been playing around with 43 inch screens and there are definitely quirks when using so many pixels
ffor example is impossible to get proper mapping on two, side-by-side 43 inch monitors even with high-end graphic cards, specifically high-bandwidth cables and the most current NVIDIA and display drivers.
Intag’s will work with one 43 inch screen and two 30 inch screens but I don’t view this as your product problem.
I’ve encountered a strange bug with my custom overlay. when I use the command “show overlay” the overlay shows up but also the automated intags continue to create a separate set of numbers until I use the command “close numbers”. Also if I switch to a newr window and execute the command to show the Intag’s, they will show up on the new window but the custom overlay on the other window does not close. When I switch focus back to the window with the overlay there are automatic tagging again in addition to the overlay.
“mouse over” doesn’t work on the custom overlays but it does work on an auto tagged window.
When I “show intags” on a new window the original custom overlay does not close. Furthermore if I execute the command “mouse over” the mouse moves to the number on the custom overlay when that command won’t move the mouse to that number on the custom overlay if it is the only one that is open
We are aware of this bug. It cropped up in the latest version of VoiceComputer.
We will fix it in the next release. In the meantime if you open an overlay, close the overlay before you invoke InTags.
You can switch from InTags to your overlays, but the bug prevent you from reversing that.
Avoid InTags in one window and overlays in a second.
This version of VC is slightly slow in refreshing the intags
Can I change the size and color of the Chrome intags
I also noticed a slightly slower refreshing of the intags.
ookay I reset back to a reopen time of 800 ms and that seems pretty much to be the same as before
the problem I have with the Intag’s on Google Chrome is that the transparency is such that on most of the custom applications that I have to use have colored backgrounds. That means instead of looking white the background looks dingy gray and it’s hard to read the numbers. Even the numbers usually look like a washed out purple.
That’s why use yellow background with black letters. tthat wouldn’t be a problem with normal content webpages but it’s a problem for me
I also would not want to have a single word or short command names because I always run into trouble with those
This is somewhat subjective but it seems that this release is more sensitive to having multiple Select-and-Say windows open and when switching between them I have had more DNS 13 hangups and crashes than I did with the previous version (at least I think so)
First, AUTO REOPEN DELAY is in terms of milliseconds. Going from 1100 to 800 only reduces it by 300 ms, or a little more than one quarter second. It may make a difference in terms of VoiceComputer's auto refresh, but it won't make any difference in terms of InTag commands, such as "InTag window" or "Show Numbers", or "Refresh Numbers"etc.
Second, your DVC command to manage the bug related to the necessity to close overlays before reissuing InTags commands is a good Band-Aid approach for the time being. As Ron points out, this was broken in the current release because previous releases automatically shut down overlays when you issue the InTags commands and vice versa. Just remember that once we fix this, you need to get rid of that command because the process of switching back and forth between overlays and InTags is faster when the switching is done by VoiceComputer.
Third, keep in mind that using single word or single syllable commands will create some conflicts. For example, if you're in notepad in you issue the command "close", it can result in closing notepad when you don't want to do that. Also, "show" is a frequently use trigger word in some applications and/or add-ons. Generally not a good idea. We can and will make some changes, but if you make the changes to these commands, we're not going to do it, and you are basically "G'd night ya on ya own". We have to keep things consistent simply because not every user of VoiceComputer has your understanding and expertise.
so where is the Chrome opacity setting in the config files.