Entry corrected on TurkeyDay.
The problems mentioned below are not problems.
They were caused by not remembering the correct commands.
It'd be really nice if Celestia complained instead of doing nothing, however.
=====================
Some of the Windows command line options no longer work for Celestia v1.3.1pre11.
.\celestia -once
does not pass the command line to the running copy of Celestia.
Instead, a second copy of Celestia is started.
.\celestia -c demo.cel
does not pass the name of the script to Celestia.
demo.cel is not run.
This is because the commands are
--once (two hyphens)
and
-u (not -c)
Maybe if I used them more often, I'd remember those not-so-subtle details.
*sigh*
Celestia v1.3.1pre11: Windows command line works
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
Celestia v1.3.1pre11: Windows command line works
Last edited by selden on 27.11.2003, 20:09, edited 2 times in total.
Selden
Re: Celestia v1.3.1pre11: Windows command line fails
selden wrote:.\celestia -once
does not pass the command line to the running copy of Celestia.
Instead, a second copy of Celestia is started.
Hmm... Did you try "celestia --once" (two dashes)? Can't test myself right now, but according to the source that could be the problem.
[Seems my answer doens't fit the answer anymore, but I'll leave it like that ]
Harald
Last edited by Harry on 28.11.2003, 00:30, edited 1 time in total.
selden wrote:You're right, of course.
Thanks for the reminder.
I hadn't used that feature for quite a while and had forgotten the need of two hyphens.
but "-c" still doesn't work
but "-u" does just fine.
I am not sure where the "-c" is from. The celestia-method which checks the command-line arguments under windows knows about:
--verbose, --fullscreen, --once, --dir and -u
Maybe I missed something, but I think that's all.
Harald
-
Topic authorselden
- Developer
- Posts: 10192
- Joined: 04.09.2002
- With us: 22 years 2 months
- Location: NY, USA
Harry,
I can only blame it on brain fade on my part.
I've corrected the first entry above in this thread and updated Preliminary User's FAQ #15 to show the correct command line options.
I can only blame it on brain fade on my part.
I've corrected the first entry above in this thread and updated Preliminary User's FAQ #15 to show the correct command line options.
Selden