I receive this error in the command editor when i open up a command to edit.  I tried to open multiple different commands and it appears to be the same error.
On a side note,  The new collection option is awesome.  Makes managing easier. Thanks

Couldn't upload picture from work.  here it is

Thanks Keith. Weirdness.

Would you mind emailing James your voicecommands.xml file for testing?

Was any of the command xml ever edited by hand, or something like that?

I just did a fresh install on a completely different pc and I am getting the same thing. I used the basic config.  Both machines are windows 7 and pretty current on updates. 

On the fresh install, i cleared out all the commands,saved,restarted. Then created a new command. same issue. 

So I am thinking my xml may not be of help.  If you still need it, let me know.

Yeah, it may not, but the thing is we have done extensive testing with this version using both fresh installs and updates so I don't really understand what is going on over there.

The error you posted is not really enough information for me to know where this is coming from.  Without being able to recreate the problem somehow I don't see how I can fix it.

I just tried it on a xp vm. getting the same error.  I'll keep investigating my end.

VC won't really run on XP anyway as far as I know.  I would expect you to have trouble before even getting to the editor.

What can you tell us about your system?

which OS?
is it 32bit or 64bit
is it a virtual machine?
what language is the OS
what languages are you using with VC for display

etc.

Do you have .Net framework 4.5 installed?

the windows 7 boxes I am using are
physical
64-bit
.net 4.5.1
Language is English all around.
Current windows updates.
very different software setup as one is my home pc and the other is work.
I have admin access on both pc's
both using forefront a/v.  home pc has vox excluded from scans

I only used the xp machine as a test to see if i could recreate it.

I just fired up my backup of 2.1.0.8 and it works fine.

Let me know if you want to test anything.

after you see the error, can you click OK and continue?

Quote from: jitterjames on November 19, 2014, 12:27:48 PM
after you see the error, can you click OK and continue?

I think the answer to that was yes.  Kind of important info!

I believe I have figured this out.  All you need to do is click OK, then adjust the font size slider once and the message will go away permanently.  I will also fix this in the next release.

thanks.

the answer is yes.  It just popped up the error. Clicking ok allowed for full editing.  
edit- Just tested the font size editor, and yes changing it fixed it.

 

Awesome. Thanks for the bug report, Keith, and for answering questions so promptly.

What she said!