BTW, this host is on a modem connection, but it's usually connected during
the daytime for you guys. It should not be pointed to as a reliable
distribution or mirror point, of course.

Miguel Albrecht wrote:

> Thank you very much for porting skycat to linux. We will put a copy of
> your binaries on the distribution directory and add a note on the
> skycat home page about it. Do you have some personal homepage to which
> we can point to?

hmmm, probably ok to just point to "http://www.cs.duke.edu/~si/"
I use my home page at CFHT for work stuff. If you want to point
to that instead, you can just point to "http://rpm.cfht.hawaii.edu/"
Or just the email address "isani@cfht.hawaii.edu" is fine too.

>
> We will look at including your changes into the core version as soon
> as we get a quiet minute -- next week is going to be very busy because
> we are hosting a collaboration meeting with the Gemini guys here
> I am sure they will like the good news as well.

You said the "c" word!!!! Wow. I feel we don't hear that one around
here at CFHT enough. It's silly to duplicate work like this, plus I
don't think many telescopes can afford to _not_ collaborate. Anyway,
I digress.

Before I forget, there were a couple of things about skycat that I
had noticed. These aren't necessarily bugs. I just haven't had any
time to explore them:

- In the file selection box, if you just specify a directory
as a filter, it should probably assume a * after it, or it
can be rather confusing.

- I think there might be an offset-bug with Pick Object when
there is a black padding area to the left of the full image.

- If the network was down when you first started skycat, it seems
there are no hosts in the catalog menus except for a couple ESO
ones. Even after the net is back up, I couldn't get these to
re-appear without restarting skycat.

- Especially on Linux, many people run various visuals and depths
which skycat is not going to like. Instead of crashing on some
cryptic "BadAccess" X error when it finally tries to install a
colormap, it could probably detect this and print a sensible
message like "skycat: requires 8-bit PseudoColor graphics display".
This might avoid some help mail from people.

More importantly, whenever the default visual is not PseudoColor,
it should ask the XServer for it (Tk_SetWindowVisual?) because
there are some TrueColor and StaticColor displays (even 16 and 24
bit) which can simultaneously support PseudoColor if the application
simply asks for it. (My display happens to be one of these cases...
I run it in StaticColor mode by default, so to run Skycat, I have
to restart my X-Server first, even though it shouldn't really be
necessary.) I'm pretty sure Tk_SetWindowVisual is the right call
to make, but I just don't know where in your code that should happen.

Be seeing you,

- Sidik