Hi folks,

Larry, thanks for the pointer on the 'go to star' bug. Problem was,
Guide would translate a given star name to its Hipparcos number, then
look in the Hipparcos catalog for position/proper motion data for that
star. A nice idea, but it only works if you've got the first CD in
the drive, _or_ you've gone to Extras... Install to Hard Drive and
selected the 'Star comments in More Info (121 MBytes)' option.

I've revised this so that if Guide lacks Hipparcos data, it
can still make use of the positional data it _does_ have (which
unfortunately does not include proper motion data, so you'll see
stars exactly where they were on 1 January 2000.)

I was unable to puzzle out the eclipse-finding bug, mostly because
the code had grown more complex than it ought to be. I ripped out
the bad part, rewrote it "logically" with the benefit of knowing
how to do it badly, and the result works just fine.

PLEASE NOTE that I have NOT POSTED THESE FIXES YET. I've still a
few odd things I'd like to get working properly first. I will post
a comment here when a "test" update is ready to go.

Ray, about calendar/planet names in the legend, you wrote:

"...If you present planet name and calendar type into the legend
only when it isn't the 'right' one, your users will have to know
your rule."

What I mostly wish to accomplish here is to ensure that people
are alerted when using a "non-standard" choice. The "(Greg.)" or
"(Mars)", for example, tells people: "WARNING: the calendar
or planet of choice isn't the 'usual' one." Ideally, it should
be accompanied by a blinking red light and a siren, but that might
be a bit much.

Denis, the idea of having a location name on the title bar seems
reasonable to me. At present, the only use made of the title bar
is either to tell you that you're running Guide 8.0, or to give you
the "hint" text when you move the cursor over a toolbar button or
legend item. I still like that idea, but there's no reason, in
theory, that Guide couldn't show "Guide 8.0 -- Helsinki, Finland"
instead of just "Guide 8.0". (But it'll wait until I post a bug
fix update!)

-- Bill