Windows file associations

This might be a little picky, but after an install, there are a lot of
filetypes associated with Dolphin -- i.e., .img, .pac, .pak, .pax, .cls, and
.st (I think that's all of them).  When I want to look at an st or cls or
pac file, I want to just double-click on it in Explorer and have notepad
come up, so I tend to remove most of the associations that Dolphin sets up.
The only one I really want there is .img->Dolphin.  (I haven't been using
pak or pax.)  Does anyone really want .st or .cls or .pac associated with
Dolphin?

Louis.

> pak or pax.)  Does anyone really want .st or .cls or .pac associated with
> Dolphin?

I occasionally use the pac association to start up the image on a specific
package. I've got a number of utilities that I run from the development
environment, to allow me to easily make changes in the way the operate, and
it's quicker for them.

I wouldn't mind being able to double click on an st file and have it
automatically open the image and then do a file-in, rather than just opening
in a workspace.

Can't see much use for cls though...

Regards
    Ian

"Louis Sumberg" <[hidden email]> wrote in message
news:[hidden email]...
> This might be a little picky, but after an install, there are a lot of
> filetypes associated with Dolphin -- i.e., .img, .pac, .pak, .pax, .cls,
and
> .st (I think that's all of them).  When I want to look at an st or cls or
> pac file, I want to just double-click on it in Explorer and have notepad
> come up, so I tend to remove most of the associations that Dolphin sets
up.
> The only one I really want there is .img->Dolphin.  (I haven't been using
> pak or pax.)  Does anyone really want .st or .cls or .pac associated with
> Dolphin?

I am inclined to agree. We will be revisiting the installation having
acquired a full-blown (read "very expensive") installation builder tool.

Regards

Blair

A couple other problems:

 - if your image is already open, it tries to open it again when you click
an associated file.
 - if you have multiple images you can really only associate with one (I
admittedly have no solution)

jlo

"Louis Sumberg" <[hidden email]> wrote in message
news:[hidden email]...
> This might be a little picky, but after an install, there are a lot of
> filetypes associated with Dolphin -- i.e., .img, .pac, .pak, .pax, .cls,
and
> .st (I think that's all of them).  When I want to look at an st or cls or
> pac file, I want to just double-click on it in Explorer and have notepad
> come up, so I tend to remove most of the associations that Dolphin sets
up.
> The only one I really want there is .img->Dolphin.  (I haven't been using
> pak or pax.)  Does anyone really want .st or .cls or .pac associated with
> Dolphin?
>
>

> > pak or pax.)  Does anyone really want .st or .cls or .pac associated
with
> > Dolphin?
>
> I occasionally use the pac association to start up the image on a specific
> package. I've got a number of utilities that I run from the development
> environment, to allow me to easily make changes in the way the operate,
and
> it's quicker for them.
>
> I wouldn't mind being able to double click on an st file and have it
> automatically open the image and then do a file-in, rather than just
opening
> in a workspace.
>
> Can't see much use for cls though...

Another data-point:

For me, all the associations (with the exception of .img) are actively
counter-productive.

Since I nearly always have Dolphin open anyway, opening that session again
is the *least* useful possible response (well, within reason anyway -- I
suppose that it'd irritate me a lot more if it fdisked my C: drive...).

The .img association isn't actually counter-productive, but I don't use it
either since I (99% of the time) start Dolphin from one of several shortcuts
with the image name embedded in the command line.

    -- chris

Chris,

> The .img association isn't actually counter-productive, but I don't use it
> either since I (99% of the time) start Dolphin from one of several
shortcuts
> with the image name embedded in the command line.

Having shot myself in the foot with it during the D4 betas, I consider the
.img association and the concept of loading the most recent image to be
dangerous.  The VM version check on load would ease that considerably.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

Bill,

> Having shot myself in the foot with it during the D4 betas, I consider the
> .img association and the concept of loading the most recent image to be
> dangerous.  The VM version check on load would ease that considerably.

I sort of agree -- I certainly find the automatic re-load adds considerable
scope for error (which is why I *never* use it -- there are no shortcuts in
my menu that don't have the image filename hardwired), and I don't think
that the version check would make a lot of difference to me (since it's only
at times like these that I am using more than one version of Dolphin at a
time).

OTOH, it is consistant with the way a number of other Windows apps work --
Visual Studio comes to mind.

Possibly some day (not D5) it could be made configurable (like VS), but that
too opens a can of worms with some options stored in the image and some in
the registry.

> Bill

    -- chris