When clicking on view cashed log files HFM can not read client names past a space it can read and find Q9650 but not read and find Q9650 @ 4.2Ghz

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Click on Clients then View cashed log files
2.
3.

What is the expected output? What do you see instead? If I click on a 
client name that does not have a space in it the log file opens, such as 
Q9650. If it does have a space in it such as Q9650 @ 4.2Ghz I will receive 
a pop-up message C;/users/Rick/appdata/roaming/hfm/logcashe/Q9650/ cannot 
find this file please verify that the correct path and filename are given.

It does not appear to be able to read past the space.

What version of the product are you using? On what operating system?
0.4.9 - Revision 154 but it also happened with the previous version

Please provide any additional information below.

Original issue reported on code.google.com by rickclif...@hotmail.com on 12 Mar 2010 at 4:04

[GoogleCodeExporter]

It's not the space, I used client names with spaces, but more likely the @ 
symbol. 
I'll have to confirm.  Thanks for the report!

Original comment by harlam357 on 15 Mar 2010 at 4:03

[GoogleCodeExporter]

@ characters are not legal in for instance names in HFM.  The UI won't allow 
you to
input these values.  The only way you could get this value into the HFM would 
be to
edit the .hfm (xml) file manually.

I am adding code to catch these names with invalid characters when loading the
configuration file.  However, I will not be expanding the Instance Naming 
scheme at
this time - I will look into it in the future.

Marking WontFix

Original comment by harlam357 on 28 Mar 2010 at 8:48

• Changed state: WontFix

[GoogleCodeExporter]

Original comment by harlam357 on 23 Mar 2012 at 4:32