Rise/transit/set as 'wait' command argument

This feature currently does not exist. If you create a bug report describing exactly how you want the feature to work we can track that for the wish list.

As a workaround, you should be able to have your script stop at the correct time (local noon) if you start from a defined time on any date. Use UTC to avoid daylight savings changes.

Rob

Workaround is good but only if I will update the script in regular manner, every day or few days at least to be correct as possible. I have to manually check sunrise/transit/sunset time, change time in script, add 'wait duration' with exact amount of seconds (manually calculated for each date) between rise and transit plus transit and set. It's quite complex and time consuming approach.

I think Nightshade has implemented function for calculating rise/transit/set time of the Sun for given place on Earth or other Solar System body.

What I meant was that you could always start at some defined time, say
midnight on the current date. Then have the script advance time until
mean local noon. But maybe that doesn't fit your needs.

There is not currently any rise/transit/set calculation going on in
Nightshade. Just body positions and orientations are calculated, which
produce those events.

A developer of our group has implemented a piece of code doing this in real time but it hasn't been added to the trunk at the moment (we are waiting for NS12). It's a good idea to try to add it in the scripting commands, as there are some needs about it for sure. You'll get it working soon enough probably.

@Rob: workaround you've proposed is standard way but yes, in this case it doesn't fit my needs. From Lionel's reply I see some other people think it would be nice feature.

I filled bug report about this: https://bugs.launchpad.net/nightshade/+bug/1035836

I'm agree this is an important and necesary feature.

I agree with Rob that using it in a wait command would be difficult and hasardous to do the job.
What I propose would be to have a command that move the date to the rise/set/transit of the sun.
That's correponding to the needs of many users. Other options would be more complex and not that useful.

@Lionel: I agree with your proposal - new argument to 'date' command rolling the sky to particular phenomenon moment. 'wait' command was an example; if it is hard to code or even dangerous it could be other command.