I find the application startup script setting confusing.
The default behavior is to try to open .slicerrc.py file with the editor registered for .py extension. If the user never actually done anything with .py extension, the click doesn’t do anything, but throw an error:
ShellExecute ‘file:///C:/Users/Murat/.slicerrc.py’ failed (error 31), even if the file exists.
As a user, I was expecting the open icon not actually try to open and edit the file, but give me a file browser that I can navigate to and choose to use with Slicer. We are distributing a .slicerrc.py file that we find useful for working with large datasets (disable compression etc…) that other can benefit from. But most of our users are never going to actually edit a python code. So the intention is that they simply navigate to it.
Can this be altered?