Lukáš Dobyvatel Posted January 28, 2014 Report Share Posted January 28, 2014 Hello everybody, I cannot see BranchExplorer from any of my workspaces. It used to work normally and one day it writes "Input string was not in a correct format", when I try to see the tree. Do you know what might be wrong ? I work on Win7 and have PlasticSCM 5.0.44.505. Thank you for any help Lukáš Link to comment Share on other sites More sharing options...
manu Posted January 29, 2014 Report Share Posted January 29, 2014 Hi Lukas! I think something is wrong with your configuration files :S Please try removing from your HD the files (or backup them), before removing them close the GUI: branchexplorer.cfg hidden_branches.conf replicationsourcesinfo.conf Then try to open the GUI & the branch explorer. Link to comment Share on other sites More sharing options...
Lukáš Dobyvatel Posted February 3, 2014 Author Report Share Posted February 3, 2014 Hello Manu, thank you for your help. It works now. Best regards Lukáš Link to comment Share on other sites More sharing options...
manu Posted February 5, 2014 Report Share Posted February 5, 2014 Cool! Sometimes a file gets "corruped" and the branch explorer doesn't work... We'll try to find out how to reproduce it! Link to comment Share on other sites More sharing options...
blile Posted August 8, 2014 Report Share Posted August 8, 2014 I got the same "Input string was not in a correct format" error just now, and I think I was able to pinpoint the problem. My 'branchexplorer.cfg' had this line: display.properties.zoom=0.9 When I changed it to display.properties.zoom=0,9 The error went away. Link to comment Share on other sites More sharing options...
calbzam Posted August 12, 2014 Report Share Posted August 12, 2014 Wow, Ok, thanks for reporting. If you also find a scenario where this issue could happen, please let us know Regards, Carlos Link to comment Share on other sites More sharing options...
JakubH Posted January 22, 2015 Report Share Posted January 22, 2015 This happens to me too. It has the same reason. I had changed locale settings in Windows control panel from "." as a decimal separator to "," and Plastic wasn't able to reflect the change. A comma is used in some locales instead of a dot. Link to comment Share on other sites More sharing options...
calbzam Posted January 22, 2015 Report Share Posted January 22, 2015 Hi JakubH, Could you give me more details about the local settings you changed in order to reproduce the issue? Regards, Carlos. Link to comment Share on other sites More sharing options...
JakubH Posted February 3, 2015 Report Share Posted February 3, 2015 In Windows Control Panel -> Region and Language -> Formats -> Additional settings... -> Numbers -> Decimal symbol – I changed from a dot to a comma. Link to comment Share on other sites More sharing options...
calbzam Posted February 4, 2015 Report Share Posted February 4, 2015 Hi, I could finally reproduce this issue. We are going to create a task to fix it asap. Thanks for reporting! Regards, Carlos. Link to comment Share on other sites More sharing options...
Willem Posted January 5, 2017 Report Share Posted January 5, 2017 Hi guys, Late to the party.. but I just ran into this same error message and cause on Plastic SCM 5.4.16.782. I installed Windows 10 with Dutch locals. Then used Plastic SCM with no issues. Until I change the comma decimal symbol to a dot. The comma is default for Dutch but since all the software I use is English and I do some coding/math I'm used to the dot as a decimal symbol. Changing the value in branchexplorer.cfg fixed the issue. Thanks for that information! This error causes several tabs to be invisible with no way to fix or change anything in the GUI. I couldn't find a related fix in the release notes from the version I use up to the current release. If this inconsistency is found in cfg files, could it be either converted or set to a default value instead of breaking the GUI? Cheer, Willem Link to comment Share on other sites More sharing options...
calbzam Posted January 5, 2017 Report Share Posted January 5, 2017 Yes, this is definitely something we need to fix. Thanks for reporting again! Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.