In case neither data folder at system nor at user level is present, Hydrogen is pretty useless. However, there is no indication (apart from log messages) what is going wrong. Especially for first-day users requiring to inspect the logs is a little bit much.
Instead, Hydrogen does check now whether the hydrogen.conf file exists on system and user level and returns with code 1 instead of starting up in case none of the two could be found. It also shows a critical pop dialogs stating "No [hydrogen.conf] file found. Hydrogen was not installed properly. Aborting...".
On the other hand, I also do not want to restrict usage too much. In addition to aborting, Hydrogen writes a new preferences file at user level too. This way the popup + exit will just occur once.
In case no drumkits are present (e.g. a first run of Hydrogen with its data folder not properly installed on system level) Song does not contain any components. The InstrumentEditor needs to take this into account. Previously it segfaulted.
In case neither
datafolder at system nor at user level is present, Hydrogen is pretty useless. However, there is no indication (apart from log messages) what is going wrong. Especially for first-day users requiring to inspect the logs is a little bit much.Instead, Hydrogen does check now whether the
hydrogen.conffile exists on system and user level and returns with code1instead of starting up in case none of the two could be found. It also shows a critical pop dialogs stating "No [hydrogen.conf] file found. Hydrogen was not installed properly. Aborting...".On the other hand, I also do not want to restrict usage too much. In addition to aborting, Hydrogen writes a new preferences file at user level too. This way the popup + exit will just occur once.
In case no drumkits are present (e.g. a first run of Hydrogen with its
datafolder not properly installed on system level)Songdoes not contain any components. TheInstrumentEditorneeds to take this into account. Previously it segfaulted.