Hi Dennis,

To continue:

I've just revised Guide so you can edit 'guide.dat' and add, say,

USER_HORIZON=30

to set the "horizon" to be at altitude 30 degrees. Objects
will rise at correspondingly later times and set earlier; the
dec limits at which objects become circumpolar and "never
visible" will rise 30 degrees. You'll see this the next time I
post an update.

(This will probably cause someone to suggest that the rise/set
times ought to reflect the user-added horizon. People who have added
their own horizons, showing the mountains, buildings, etc. blocking
their views, have occasionally asked about this; it would be nice
to know that "the target will come out from behind that tree at xx:xx."
It'd be nice, but probably won't happen too soon!)

For the LX-200, I'm contemplating having Guide set the date/time
and/or latitude/longitude from the PC (for non-GPS scopes), as well
as functions to set the PC's date/time and Guide's lat/lon from the
scope (for GPS scopes.) I just took a fresh look through the LX-200
command set, and see all sorts of nifty things that could, in theory,
be set from within Guide (multiple observing sites, their names
and positions, synching on lunar features, getting raw GPS data
so you can get a _really_ precise time set on your PC, set
arbitrary slew rates (only on the GPS scopes), some others...
dunno how much of all this I'll tackle, though.)

-- Bill