IPFS settings locked until successful startup

[karalabe]

When starting up Akasha, the settings fields for IPFS are disabled until the process successfully starts up:

This is a problem, because the reason I'm there in the first place is to change the settings, which conflict with another instance of IPFS running on my local machine, causing IPFS not to be able to start. Hence we're in a vicious circle, where I can't start IPFS due to setting conflict, but I can't change the config due to not being able to start it :P

[kenshyx]

The ipfs config is modified using the rpc api, thats why it needs the node to be started. Another way to modify it(using ipfs config) is not consistent across all platforms and sometimes it hangs. The last method to modify the ipfs config is to manually edit the config file located in .ipfs folder.

[karalabe]

Well sure, but if I can't start IPFS due to a port clash, then I can fix the issue either.