mgedawson2000 Mar 12, 2002
> Wups! Forgot to mention:HOTKEY.DAT
>
> Matt, about the missing Alt-C link to Charon: try editing
> and looking for the Alt-C line, and changing it to readbe
>
> Alt-C A 46 2344 A 67 2355 *
>
> The meaning of all this (and a more general discussion of how to
> change hotkeys) is at
>
> http://www.projectpluto.com/hotkeys.htm
>
> However, you may wish to just wait a day or two, when it will
> possible to reset hotkeys from within Guide. A clip from the text
> describing the next update:
>
> ----------- Clip from Web site ------------
> (?? Mar 2002) Ability to reset hotkeys:
> It has long been possible for sufficiently devoted people to reset
> the hotkeys in Guide by editing a text file (click here for
> details). This is user-abusive enough that I doubt many people
> have done it.
>
> In the current version, there is a new "Choose Hotkey" button in
> the Settings... Toolbar dialog. By default, it is grayed out.
> Click on a function in the list in that dialog, and the button
> shows the hotkey currently associated with that function (or a
> non-grayed-out "Choose Hotkey" if none is associated with it.)
> Click on the button, and Guide brings up a list of possible
> hotkeys (and their current functions). Choose one of those
> hotkeys, and Guide will thenceforth perform that action when that
> hotkey is pressed.
> ----------- Clip from Web site ------------
>
> About the odd A2.0 star colors: this is quite odd... do they
> return to white if the "Color Stars" option is not checked in the
> Star Display dialog? While the poor photometry in A2.0 leads to
> odd colors (bluer-than-blue and redder-than-red stars), they should
> at least show up in "normal" spectral colors.
>
> Switching the video mode may help. Some people have reported
> weird cases where, in 256-color modes, Windows couldn't find a
> "good" color and chose the nearest (sometimes not too near)
> approximation. I've also heard of such things happening in 16-bit
> color modes, which makes no sense to me at all.
>
> -- Bill