Hi Bill,

Maybe the idea of having file names in the .NOT files has been a little
bit over estimated in the following mails. I thing it's probably simpler
that it appears (but I might be totally wrong). If I had to do it, I
would just pass the filename (or url or whatever) to the ShellExecute()
system function. That one will open the default application associated
with the file extension. That's the same as double clicking a file name
in the file explorer. Maybe worth a trial ?

Thanks a lot for the great work you are doing, Claude

> -----Original Message-----
> From: Bill J. Gray [mailto:pluto@...]
> Sent: Sunday, August 06, 2000 7:50 PM
> To: guide-user@...
> Subject: [guide-user] Images, index, Almagest, etc.
>
>
> Hi folks,
>
> Claude mentioned adding images in the .NOT files... not a bad idea,
> although (as he mentioned) this doesn't work yet. In theory, I may
> rig up Guide to pass such requests to a browser (the idea being that,
> when you click on a link with a file extension such as .html, .gif,
> etc., your browser would come up with that link loaded).
>
> Ideally, Guide's help system should have been HTML-based from the
> beginning. (I had to abandon any idea of a Windows-based help system;
> you can't dynamically alter such a help system, the way Guide does
> routinely when you click for "more info" on an object or generate a
> table of events.) It would actually have saved me a bit of
> work, since
> I would have written only the code required to create .HTML
> files, not
> the code to display them. But at this point, such a
> revision would be
> a Big Problem.
>