You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ConsoleZ closes without explanation on bad config #358
I have seen this problem in three scenarios at different times (the third being the most recent):
XML formatting errors (unclosed tags, caused by bad copy)
This case only occurs when user modify the configuration file by himself.
Last versions of ConsoleZ start by ignoring the corrupt file. I can add an error message popup too.
XML structure changes (caused by copying an old console.xml to a new install)
Strange... configuration file is always backward compatible. I can use my current configuration file with the old Console2 application. And I can use Console2 configuration file with every ConsoleZ version.
Missing shell exe (caused by an upgrade to new msysgit, which installed to a new path)
Yes we can start a failover shell when zero shell has started.
Case #2 might also be related to Case #1 so we can probably ignore it. Having an error popup in case the file is unreadable for any reason would be a huge help.
If you start ConsoleZ with a broken configuration file, you will use default configuration. So when you save the configuration (by editing settings, selecting views, …), broken file is replaced by new one.
Should we (only when configuration file is broken):
ask for replacement when saving the configuration file?
Activity
cbucher commentedon Aug 4, 2016
This case only occurs when user modify the configuration file by himself.
Last versions of ConsoleZ start by ignoring the corrupt file. I can add an error message popup too.
Strange... configuration file is always backward compatible. I can use my current configuration file with the old Console2 application. And I can use Console2 configuration file with every ConsoleZ version.
Yes we can start a failover shell when zero shell has started.
Whiteknight commentedon Aug 4, 2016
Case #2 might also be related to Case #1 so we can probably ignore it. Having an error popup in case the file is unreadable for any reason would be a huge help.
cbucher commentedon Aug 5, 2016
If you start ConsoleZ with a broken configuration file, you will use default configuration. So when you save the configuration (by editing settings, selecting views, …), broken file is replaced by new one.
Should we (only when configuration file is broken):
#358 Start a safe console when no console started
#358 loading/saving settings code has been rewritten
#358 Configuration file is no longer saved when user open settings di…
#358 A popup is displayed when XML parsing fails.
#358 Simplified configuration file in resource (we use default values).
cbucher commentedon Aug 18, 2016
@Whiteknight Please test last experimental release - version 1.17.1.16230
cbucher commentedon Aug 23, 2016
@Whiteknight Please try last experimental release - version 1.17.1.16236