At the moment, MUSHClient auto-associates itself with its config files (cant remember what extension they are off the top of my head). however, this makes it difficult to put it on a thumb drive. is there any way of removing/disabling this?
MUSHClient associates itself with config files
Posted by Taneth111 on Mon 02 Mar 2009 01:32 AM — 7 posts, 26,743 views.
File associations only matter when you double click on a data file. It helps windows find the associated program to open them.
Put MC on a thumb drive, and don't doubleclick on .mcl files to open your mud. Things should be fine.
Put MC on a thumb drive, and don't doubleclick on .mcl files to open your mud. Things should be fine.
I'm not totally sure where the association is done. It is in one of the internal libraries. I'm not sure what I would have to do to disable that, but could look into it, if it is a big worry.
although MUSHClient works fine from a thumb drive, its still not very professional/good/stealth to leave behind broken file associations.
I think the way Microsoft designed their libraries, they didn't really anticipate you would remove applications. After all, how can a program sensibly remove a file association? You might want to run the program tomorrow by clicking on its document. There is provision right now for deleting them by using the Tools -> Folder Options -> File types in the Explorer windows.
However to keep everyone happy (as far as possible) version 4.41 has a new command-line option:
If that is present, it skips the file type registration.
However to keep everyone happy (as far as possible) version 4.41 has a new command-line option:
/noregister
If that is present, it skips the file type registration.
It seems like a strange way to go about it.
The way it is common to do this these days seems to be as follows:
1) Installer sets up file associations (if option is checked).
2) Program leaves file associations alone.
3) If people lost their file associations, and want them restored, they go to some kind of preferences screen and hit the 'restore file associations' button.
It seems like a far saner way to go about this to be honest. :) Restoring file associations tends to be a trickier endeavour than simply changing them when asked. E.g. the policy of opt-in versus opt-out.
The way it is common to do this these days seems to be as follows:
1) Installer sets up file associations (if option is checked).
2) Program leaves file associations alone.
3) If people lost their file associations, and want them restored, they go to some kind of preferences screen and hit the 'restore file associations' button.
It seems like a far saner way to go about this to be honest. :) Restoring file associations tends to be a trickier endeavour than simply changing them when asked. E.g. the policy of opt-in versus opt-out.
Cool, thanks for that. Now to sit back and wait for the new release :P