--startup-script option doesn't work

[Matthew Gates]

The argument to the --startup-script option doesn't seem to get used.

Always there is this in the console output:

...
Creating GUI ...
"WARNING: cannot open script: "
...

The message should include the name of the file, so apparently it is not getting to the runScript function from the CLI.

[Matthew Gates (matthew-porpoisehead)]

related bug #730180

[Alexander Wolf (alexwolf)]

This bug NOT related with bug #730180.

First, look at code into StelMainGraphicsView.cpp since 279 and seen this lines:
QString startupScript;
if (qApp->property("onetime_startup_script").isValid())
                   qApp->property("onetime_startup_script").toString();
else
                  startupScript = conf->value("scripts/startup_script", "startup.ssc").toString();
scriptMgr->runScript(startupScript);

But this code NEVER getting script name from --startup-script attribution because need line "startupScript = qApp->property("onetime_startup_script").toString();" instead current "qApp->property("onetime_startup_script").toString();"

Second, if we add this line, then we have segmentation fault because QPainter called BEFORE init graphics mode.

I think this feature never worked. :(

[Ravi Hans (billoosingh15)]

I did one other thing when I could not get the script to launch propery. I modified the default startup_script (which is blank) and put my script code there. Stellarium still hung up. So the issue does not seem to be that the right script isn't getting loaded, but that something bad happens when it starts to execute.

[Alexander Wolf (alexwolf)]

So, I'm fix part one (look at http://bazaar.launchpad.net/~stellarium/stellarium/trunk/revision/5128), but part two is described on this report - https://bugs.launchpad.net/stellarium/+bug/689657